[Python-Dev] Python byte-compiled and optimized code
Fred Drake
fdrake at gmail.com
Wed Oct 7 17:12:09 CEST 2009
More information about the Python-Dev mailing list
Wed Oct 7 17:12:09 CEST 2009
- Previous message: [Python-Dev] Python byte-compiled and optimized code
- Next message: [Python-Dev] Python byte-compiled and optimized code
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, Oct 7, 2009 at 10:34 AM, Swapnil Talekar <swapnil.st at gmail.com> wrote: > 1) Is the byte-compiled .pyc file and optimized .pyo file > platform-independent?(including python versions 3.x) Yes. > If yes, is it > guaranteed to stay that way in future? Yes. > 2) If the the generation of .pyc file fails (say, due to write protected > area), does that stop the script execution? No. It only means the bytecode won't be cached. > 3) Is it possible to redirect the location of the generation of .pyc files > to other than that of the corresponding .py files? I think some support for this has been developed, at least experimentally, but I'm not sure if it's part of a stable release or not. It's more likely in Python 3.x, which I'm significantly less familiar with. -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> "Chaos is the score upon which reality is written." --Henry Miller
- Previous message: [Python-Dev] Python byte-compiled and optimized code
- Next message: [Python-Dev] Python byte-compiled and optimized code
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list