Mark Shannon <m...@hotpy.org> added the comment:
I think this can finally be closed. A mere 12 years after it was opened :) PEP 626 specifies what the correct behavior is, regardless of whether optimizations are turned on or off, so there is no point in a no-optimize option. The compiler is fast enough that it is never worth turning off, even for iterate development. If the bytecode optimizer produces incorrect or inefficient code for a particular example, please file a bug report for that case, and assign me. ---------- nosy: +Mark.Shannon _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue2506> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
