[issue27226] distutils: unable to compile both .opt-1.pyc and .opt2.pyc simultaneously

Steve Dower added the comment: Distutils is now deprecated (see PEP 632) and all tagged issues are being closed. From now until removal, only release blocking issues will be considered for distutils. If this issue does not relate to distutils, please remove the component and reopen it. If

[issue27226] distutils: unable to compile both .opt-1.pyc and .opt2.pyc simultaneously

Change by Brett Cannon : -- nosy: -brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue27226] distutils: unable to compile both .opt-1.pyc and .opt2.pyc simultaneously

Éric Araujo added the comment: FWIW the behaviour in distutils was intended to be controlled by the setup.p options, but in fact also depended on the options of the python command itself (-O and dont-write-bytecode option/envvar). This was changed in distutils2 but judged too big to fix in

[issue27226] distutils: unable to compile both .opt-1.pyc and .opt2.pyc simultaneously

Changes by Chris Mayo : -- nosy: +cjmayo ___ Python tracker ___ ___ Python-bugs-list

[issue27226] distutils: unable to compile both .opt-1.pyc and .opt2.pyc simultaneously

Changes by Brett Cannon : -- versions: -Python 3.5 ___ Python tracker ___ ___

[issue27226] distutils: unable to compile both .opt-1.pyc and .opt2.pyc simultaneously

Changes by Brett Cannon : -- type: behavior -> enhancement ___ Python tracker ___ ___

[issue27226] distutils: unable to compile both .opt-1.pyc and .opt2.pyc simultaneously

Michał Górny added the comment: Yes, you could put it like this. -- ___ Python tracker ___ ___

[issue27226] distutils: unable to compile both .opt-1.pyc and .opt2.pyc simultaneously

Brett Cannon added the comment: But distutils still does the right thing with -O2 and --optimize 2, right? If that's the case then this is an enhancement request to add support to distutils to compile all bytecode levels and not a regression. --

[issue27226] distutils: unable to compile both .opt-1.pyc and .opt2.pyc simultaneously

Michał Górny added the comment: Brett, .pyc was controlled by --compile and .pyo by --optimize (either 1 or 2). Technically only two variants could be used simultaneously, and distutils accounted for that. Now you have .pyc + .opt-1.pyc + .opt-2.pyc, so three variants instead of two.

[issue27226] distutils: unable to compile both .opt-1.pyc and .opt2.pyc simultaneously

Brett Cannon added the comment: So the reason Python does the right thing at install is because compileall is used by the Makefile to do the compilation and it's run twice (it actually doesn't use distutils for this). My question is what did distutils do before PEP 488 since .pyc and .pyo

[issue27226] distutils: unable to compile both .opt-1.pyc and .opt2.pyc simultaneously

Ned Deily added the comment: Since this is an addition to the changes made for PEP 488 (Issue23731), nosying Brett -- nosy: +brett.cannon, ned.deily ___ Python tracker

[issue27226] distutils: unable to compile both .opt-1.pyc and .opt2.pyc simultaneously

Arfrever Frehtes Taifersar Arahesis added the comment: I would suggest using --optimize=1,2 / -O1,2 for this purpose. Documentation in this part of Lib/distutils/command/build_py.py and Lib/distutils/command/install_lib.py should also be updated: ('optimize=', 'O', "also

[issue27226] distutils: unable to compile both .opt-1.pyc and .opt2.pyc simultaneously

Changes by Michał Górny : -- keywords: +patch Added file: http://bugs.python.org/file43231/0001-distutils-make-OO-enable-both-opt-1-and-opt-2-optimi.patch ___ Python tracker

[issue27226] distutils: unable to compile both .opt-1.pyc and .opt2.pyc simultaneously

New submission from Michał Górny: Since 3.5, optimized Python modules for -O and -OO are installed using different names. The Python build system itself seems to been prepared for this as Python itself is built with both .opt-1.pyc and .opt-2.pyc files built. However, distutils at the moment