➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients bukzor, docs@python, r.david.murray, terry.reedy
Date 2010-09-21.01:45:02
SpamBayes Score 1.4914389e-07
Marked as misclassified No
Message-id <1285033505.37.0.105345068012.issue9583@psf.upfronthosting.co.za>
In-reply-to
Content 
I understood the documentation snippet Terry quoted as saying exactly what you say the code does.  The doc could be clearer by replacing "multiple times" with "that number of times".  Not that more than two has any meaning currently...

Changing the behavior of PYTHONOPTIMIZE as you suggest would be a backward compatibility change that would probably require a deprecation cycle.  (And the message would have to not really be a DeprecationWarning, since DeprecationWarnings are now silent by default but this is a user-triggered event, not a developer-triggered event and so should be user visible.)

Unsetting an environment variable to remove its effect is a fairly common idiom.  So I don't think it is worth the effort of making the change you suggest, even though I agree it would be more intuitive if PYTHONOPTIMIZE=0 meant what you thought it meant.
History
Date User Action Args
2010-09-21 01:45:05r.david.murraysetrecipients: + r.david.murray, terry.reedy, docs@python, bukzor
2010-09-21 01:45:05r.david.murraysetmessageid: <1285033505.37.0.105345068012.issue9583@psf.upfronthosting.co.za>
2010-09-21 01:45:03r.david.murraylinkissue9583 messages
2010-09-21 01:45:02r.david.murraycreate