[Python-ideas] Changes to the existing optimization levels
Diana Clarke
diana.joan.clarke at gmail.com
Fri Sep 29 10:56:43 EDT 2017
More information about the Python-ideas mailing list
Fri Sep 29 10:56:43 EDT 2017
- Previous message (by thread): [Python-ideas] Changes to the existing optimization levels
- Next message (by thread): [Python-ideas] allow overriding files used for the input builtin
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I suppose anything is possible ;) Perhaps I'll try my hand at that next. But no, I'm limiting the scope to the existing toggles only (docstrings, __debug__, assert) for this pass. I am aware of that thread though. I read it a few weeks back when I was initially researching the existing implementation and history. Happy Friday, folks! --diana On Fri, Sep 29, 2017 at 6:47 AM, Ned Batchelder <ned at nedbatchelder.com> wrote: > Don't forget that the current "no optimizations" setting actually does > peephole optimizations. Are we considering addressing > https://bugs.python.org/issue2506 to make a really truly "no optimizations" > option?
- Previous message (by thread): [Python-ideas] Changes to the existing optimization levels
- Next message (by thread): [Python-ideas] allow overriding files used for the input builtin
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-ideas mailing list