Changes between and of Initial VersionVersion 2Ticket #5129
- Timestamp:
- 06/01/2011 12:47:56 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #5129
- Property Cc Facundo Batista added
-
Ticket #5129 – Description
initial v2 1 From [http://docs.pythonsprints.com/python3_porting/py-porting.html#execfile-statement porting-guide]: Starting with Python 3, the execfile statement is no longer available. An alternative is to use the compile() function in conjunction with exec(). compile() can create a code object from a file, and then it can be passed into exec().1 From [http://docs.pythonsprints.com/python3_porting/py-porting.html#execfile-statement porting-guide]: Starting with Python 3, the `execfile` statement is no longer available. An alternative is to use the `compile()` function in conjunction with `exec()`. `compile()` can create a code object from a file, and then it can be passed into `exec()`. 2 2 3 3 {{{ … … 5 5 }}} 6 6 7 Some of this work has been done by loewis in #4244, but that ticket focuses on getting setup.py to run in py3k, which involves more than execfilecompatibility.7 Some of this work has been done by `loewis` in #4244, but that ticket focuses on getting `setup.py` to run in py3k, which involves more than `execfile` compatibility. 8 8 9 Currently these modules use execfile:9 Currently these modules use `execfile`: 10 10 11 11 {{{ … … 21 21 }}} 22 22 23 where lore/htmlbook.py can be ignored because its being phased out, so it seems small enough for asingle ticket.23 where `lore/htmlbook.py` can be ignored because its being phased out, so small enough for this single ticket.