Message148499
| Author |
Arfrever |
| Recipients |
Arfrever, alexis, eric.araujo, tarek |
| Date |
2011年11月28日.16:15:08 |
| SpamBayes Score |
3.2474833e-05 |
| Marked as misclassified |
No |
| Message-id |
<1322496909.68.0.820560221731.issue13400@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Jython's *$py.class files are byte-compiled modules, not extension modules.
There should be a way to disable generation of *.pyo files on command line even if setup.cfg enables it.
IMHO it would make more sense if --optimize-bytecode was dependant on --byte-compile option:
--no-byte-compile -> No *.pyc and *.pyo
--byte-compile --optimize-bytecode=0 -> Only *.pyc
--byte-compile --optimize-bytecode=0,1 -> *.pyc and *.pyo (with docstrings)
--byte-compile --optimize-bytecode=0,2 -> *.pyc and *.pyo (without docstrings)
--byte-compile --optimize-bytecode=1 -> Only *.pyo (with docstrings)
--byte-compile --optimize-bytecode=2 -> Only *.pyo (without docstrings)
--byte-compile --optimize-bytecode=1,2 -> Error
Byte-compiled files in Gentoo are generated separately, after installation. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2011年11月28日 16:15:09 | Arfrever | set | recipients:
+ Arfrever, tarek, eric.araujo, alexis |
| 2011年11月28日 16:15:09 | Arfrever | set | messageid: <1322496909.68.0.820560221731.issue13400@psf.upfronthosting.co.za> |
| 2011年11月28日 16:15:09 | Arfrever | link | issue13400 messages |
| 2011年11月28日 16:15:08 | Arfrever | create |
|