Message162814
| 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.) |
|