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 Arfrever, alexis, eric.araujo, tarek
Date 2011-11-25.17:12:03
SpamBayes Score 0.0007596699
Marked as misclassified No
Message-id <1322241124.16.0.610286092483.issue13400@psf.upfronthosting.co.za>
In-reply-to
Content
Juste a note: currently, when a command sets one option from the value given to another command, they have the same name, with two kinds of exceptions:
- build --build-lib becomes build_lib --build-dir (etc.)
- install --install-lib becomes install_lib --install-dir (etc.)

So, introducing --(no-)byte-compile and --optimize-bytecode= would change that scheme, but it is not a big deal.

On the third hand, maybe this is an opportunity to change the option names on the build_py and install* commands too.  For example, for a long time I thought that --optimize implied --compile, but actually they’re distinct options.

BTW, would these new options simplify some scripts you have, or do you just request them for consistency?
History
Date User Action Args
2011-11-25 17:12:04eric.araujosetrecipients: + eric.araujo, tarek, Arfrever, alexis
2011-11-25 17:12:04eric.araujosetmessageid: <1322241124.16.0.610286092483.issue13400@psf.upfronthosting.co.za>
2011-11-25 17:12:03eric.araujolinkissue13400 messages
2011-11-25 17:12:03eric.araujocreate