This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients acidbase, brett.cannon, eric.araujo, loewis, ncoghlan
Date 2012-03-02.05:54:06
SpamBayes Score 2.882546e-06
Marked as misclassified No
Message-id <1330667649.16.0.531590956782.issue1346572@psf.upfronthosting.co.za>
In-reply-to
Content
> Does "compileall" generate both .pyc and .pyo by default?
python3 -m compileall generates pyc, python3 -O -m compileall pyo.  Functions in py_compile and compileall gained an optimize argument in 3.2.

> does pysetup handle that for you?
You’ll have to be more specific.  Bytecode files can be created when building a bdist or on install from source.  Packaging commands do not depend on the calling Python’s -O option, they have their own options to let users specify if they want pyc files, pyo, neither or both.

> MvL is correct that zipimport should ignore .pyo files when __debug__ is set and vice-versa, but the
> precompilation tools should also take care of generating both versions by default.
Really?  The behaviors of compileall and packaging seems better to me.
History
Date User Action Args
2012-03-02 05:54:09eric.araujosetrecipients: + eric.araujo, loewis, brett.cannon, ncoghlan, acidbase
2012-03-02 05:54:09eric.araujosetmessageid: <1330667649.16.0.531590956782.issue1346572@psf.upfronthosting.co.za>
2012-03-02 05:54:06eric.araujolinkissue1346572 messages
2012-03-02 05:54:06eric.araujocreate