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 terry.reedy
Recipients Ronan.Lamy, docs@python, eric.araujo, eric.snow, lebigot, mherrmann.at, r.david.murray, terry.reedy, vstinner
Date 2012-06-14.18:59:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1339700348.78.0.986876797613.issue12982@psf.upfronthosting.co.za>
In-reply-to
Content
Eric, can you find a place in the current doc where -O and .pyo are mentioned, and where you think a sentence should go. What sentence(s) would you like to see.

Other comments:

__debug__ is intended to be a process-global compilation value (implemented as a keyword) set on startup

>>> __debug__
True
>>> __debug__ = False
SyntaxError: assignment to keyword

The devs are not willing to support having contradictory values in the same process. Indeed, since I posted last night, the pydev discussion has moved to the question of whether -O, __debug__, and .pyo as now defined are worth the nuisance they cause or whether some or all should be deprecated. (Docstring stripping for saving space could then be a separate tool.)

---
Python interpreters exist to run Python code. The existence, persistence, and other details of compilation caches are version-dependent implementation details. Being able to execute from such caches without source present is also an implementation detail, and for CPython, it gets secondary support at best. (This is a compromise between full support and no support.)
History
Date User Action Args
2012-06-14 18:59:08terry.reedysetrecipients: + terry.reedy, vstinner, lebigot, eric.araujo, r.david.murray, docs@python, eric.snow, Ronan.Lamy, mherrmann.at
2012-06-14 18:59:08terry.reedysetmessageid: <1339700348.78.0.986876797613.issue12982@psf.upfronthosting.co.za>
2012-06-14 18:59:08terry.reedylinkissue12982 messages
2012-06-14 18:59:07terry.reedycreate