[issue13400] packaging: build command should have options to control byte-compilation

Changes by Éric Araujo : -- dependencies: -Add tests for files byte-compiled by distutils[2] resolution: -> out of date stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue13400] packaging: build command should have options to control byte-compilation

Julien Courteau added the comment: It is possible to only change the "frontend" (options: byte-compile, compile, no-byte-compile, optimize) without changing the "backend" (attributes: compile and optimize). This way it is then easy to handle both sets of options (no-byte-compile, byte-compile

[issue13400] packaging: build command should have options to control byte-compilation

Éric Araujo added the comment: One thing just came to my mind: if we change option names and people use the new names in setup.cfg or ~/.pydistutils.cfg, then the file will stop being compatible with distutils. -- ___ Python tracker

[issue13400] packaging: build command should have options to control byte-compilation

Éric Araujo added the comment: FTR I asked Julien to provide his opinion as a user and he agreed that having just one --byte-compile/--no-byte-compile option pair seemed better than the existing names (where --compile and --optimize are unrelated). I wanted to avoid --byte-compile=0 to genera

[issue13400] packaging: build command should have options to control byte-compilation

Julien Courteau added the comment: Here is the last proposition of Eric done at the last Montreal Sprint (May 12): --no-byte-compile-> No *.pyc and *.pyo --byte-compile=b -> Only *.pyc --byte-compile=b,o -> *.pyc and *.pyo (with docstrings) --byte-compile=b,oo -> *.pyc and *.pyo (wit

[issue13400] packaging: build command should have options to control byte-compilation

Éric Araujo added the comment: Thanks for all the feedback! So, for anyone interested in contributing, two patches are needed: One that changes the existing options to use the new names and parsing behavior (--no-compile, --compile[=0,1,2]) and adds tests for the erroneous --compile=1,2 (ot

[issue13400] packaging: build command should have options to control byte-compilation

Arfrever Frehtes Taifersar Arahesis added the comment: --byte-compile=arguments is a good idea. (Gentoo uses py_compile and compileall modules.) -- ___ Python tracker ___ _

[issue13400] packaging: build command should have options to control byte-compilation

Éric Araujo added the comment: > Jython's *$py.class files are byte-compiled modules, not extension modules. Thanks for the data point. Agreed distutils[2] should not say “pyc” and “pyo” then. > There should be a way to disable generation of *.pyo files on command line > even if > setup.cfg

[issue13400] packaging: build command should have options to control byte-compilation

Arfrever Frehtes Taifersar Arahesis added the comment: 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

[issue13400] packaging: build command should have options to control byte-compilation

Éric Araujo added the comment: > I suggest to not use "pyc" and "pyo" in options, because ".pyc" and ".pyo" > filename extensions > are specific to a subset of Python implementations. Jython uses "$py.class" > filename extension > (module$py.class for module.py). But these are extension module

[issue13400] packaging: build command should have options to control byte-compilation

Arfrever Frehtes Taifersar Arahesis added the comment: I suggest to not use "pyc" and "pyo" in options, because ".pyc" and ".pyo" filename extensions are specific to a subset of Python implementations. Jython uses "$py.class" filename extension (module$py.class for module.py). You could use -

[issue13400] packaging: build command should have options to control byte-compilation

Éric Araujo added the comment: Okay, I think it’s a valuable use case. (Out of curiosity, why don’t you want byte-compiled files on your system? It speeds up imports, and problems due to the presence of stray pyc files when the py is deleted are gone in 3.2+. Maybe you have custom tools to