Message148341
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? |
|
Date |
User |
Action |
Args |
2011-11-25 17:12:04 | eric.araujo | set | recipients:
+ eric.araujo, tarek, Arfrever, alexis |
2011-11-25 17:12:04 | eric.araujo | set | messageid: <1322241124.16.0.610286092483.issue13400@psf.upfronthosting.co.za> |
2011-11-25 17:12:03 | eric.araujo | link | issue13400 messages |
2011-11-25 17:12:03 | eric.araujo | create | |
|