[issue2506] Add mechanism to disable optimizations
STINNER Victor
report at bugs.python.org
Thu May 22 09:12:52 CEST 2014
STINNER Victor added the comment:
> Have you considered whether the genererated PYC files need a different magic number or some other way to indicate that they aren't production code?
Would it make sense to use a different sys.implementation.cache_tag? For example, the tag si currently "cpython-35". We can use "cpython-35P" when peephole optimizations are disabled. So you can have separated .pyc and .pyo files and the disabling peephole optimizations is compatible with -O and -OO command line options.
----------
nosy: +haypo
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue2506>
_______________________________________
More information about the Python-bugs-list
mailing list