PEP 304 lives on :) (#673)
This commit is contained in:
parent
65edc87719
commit
1a43bed5ca
15
pep-0304.txt
15
pep-0304.txt
|
@ -9,6 +9,21 @@ Content-Type: text/x-rst
|
||||||
Created: 22-Jan-2003
|
Created: 22-Jan-2003
|
||||||
Post-History: 27-Jan-2003, 31-Jan-2003, 17-Jun-2005
|
Post-History: 27-Jan-2003, 31-Jan-2003, 17-Jun-2005
|
||||||
|
|
||||||
|
Historical Note
|
||||||
|
===============
|
||||||
|
|
||||||
|
While this original PEP was withdrawn, a variant of this feature
|
||||||
|
was eventually implemented for Python 3.8 in https://bugs.python.org/issue33499
|
||||||
|
|
||||||
|
Several of the issues and concerns originally raised in this PEP were resolved
|
||||||
|
by other changes in the intervening years:
|
||||||
|
|
||||||
|
- the introduction of isolated mode to handle potential security concerns
|
||||||
|
- the switch to ``importlib``, a fully import-hook based import system implementation
|
||||||
|
- PEP 3147's change in the bytecode cache layout to use ``__pycache__``
|
||||||
|
subdirectories, including the ``source_to_cache(path)`` and
|
||||||
|
``cache_to_source(path)`` APIs that allow the interpreter to automatically
|
||||||
|
handle the redirection to a separate cache directory
|
||||||
|
|
||||||
Abstract
|
Abstract
|
||||||
========
|
========
|
||||||
|
|
Loading…
Reference in New Issue