[issue23892] Introduce sys.implementation.opt_levels

Eric Snow added the comment: There are (solvable) problems with my original recommendation: 1. sys.implementation is by definition not suitable for third-party import hooks to modify + it is set during the Python implementation during runtime init + it is effectively read-only after that

[issue23892] Introduce sys.implementation.opt_levels

Eric Snow added the comment: (Sorry for taking so long!) Thanks for doing this, Cheryl! I'm leaving a review on your PR. :) Also, in PEP 421 it says that you need a PEP for this. [1] "Such a PEP need not be long, just long enough." (I just realized that the requirement isn't obvious so I

[issue23892] Introduce sys.implementation.opt_levels

Cheryl Sabella added the comment: Brett, I know you're away this month, so please ignore this, Eric, I hope the changes I made reflect your original intent in the code review for #23731. This is my first change to the C code, so I hope it's close. The tests passed, so it must be correct.

[issue23892] Introduce sys.implementation.opt_levels

Change by Cheryl Sabella : -- keywords: +patch pull_requests: +9201 stage: test needed -> patch review ___ Python tracker ___ ___ Py

[issue23892] Introduce sys.implementation.opt_levels

Changes by Brett Cannon : -- dependencies: +Implement PEP 488 title: Introduce sys.implementation.opt_levels ? -> Introduce sys.implementation.opt_levels ___ Python tracker ___

[issue23892] Introduce sys.implementation.opt_levels ?

New submission from Brett Cannon: Eric suggested in a code review for issue #23731 that maybe we should have the possible optimization levels listed somewhere. -- components: Library (Lib) messages: 240286 nosy: brett.cannon, eric.snow priority: low severity: normal stage: test needed s