[issue33501] split existing optimization levels into granular options

STINNER Victor added the comment: I'm not sure that the bug tracker is the best place to propose such idea. Maybe start a new thread on python-ideas? -- ___ Python tracker

[issue33501] split existing optimization levels into granular options

Brett Cannon added the comment: I don't thnk they are quite the same. The other issue is about turning off the peepholer entirely while this one is about breaking up the optimizations that -O and -OO do so you can choose which ones you want (e.g. still drop docstrings but

[issue33501] split existing optimization levels into granular options

Serhiy Storchaka added the comment: Isn't this a duplicate of the old issue2506? -- nosy: +serhiy.storchaka ___ Python tracker

[issue33501] split existing optimization levels into granular options

Nick Coghlan added the comment: PSF link for Diana Clark's thread on python-ideas about this: https://mail.python.org/pipermail/python-ideas/2017-September/047224.html (this is the same thread Brett linked, just to the PSF archives rather than Google Groups) --

[issue33501] split existing optimization levels into granular options

Brett Cannon added the comment: Reference to some discussions on this topic https://groups.google.com/forum/#!topic/python-ideas/4oRgwrV1tVA -- ___ Python tracker

[issue33501] split existing optimization levels into granular options

Change by Steven D'Aprano : -- nosy: +steven.daprano ___ Python tracker ___ ___

[issue33501] split existing optimization levels into granular options

New submission from Carl Meyer : It doesn't make sense for e.g. docstring-stripping to necessarily imply assert-stripping. These are totally separate options, useful for separate reasons, but currently tied together in the `-O` option. This is not just a theoretical problem;