Changes between and of Initial VersionVersion 2Ticket #5129


Ignore:
Timestamp:
06/01/2011 12:47:56 PM (8 years ago)
Author:
Thijs Triemstra
Comment:

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().
     1From [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()`.
    22
    33{{{
    … …  
    55}}}
    66
    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.
     7Some 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.
    88
    9 Currently these modules use execfile:
     9Currently these modules use `execfile`:
    1010
    1111{{{
    … …  
    2121}}}
    2222
    23 where lore/htmlbook.py can be ignored because its being phased out, so it seems small enough for a single ticket.
     23where `lore/htmlbook.py` can be ignored because its being phased out, so small enough for this single ticket.