add a note about my ignorance of import hooks and how they relate to this
pep. add posting date, as it's about to be announced to the unwashed masses...
This commit is contained in:
parent
9c13bfc40f
commit
73a95274f5
|
@ -7,7 +7,7 @@ Status: Active
|
|||
Type: Draft
|
||||
Content-Type: text/x-rst
|
||||
Created: 22-Jan-2003
|
||||
Post-History:
|
||||
Post-History: 27-Jan-2003
|
||||
|
||||
|
||||
Abstract
|
||||
|
@ -188,6 +188,10 @@ Issues
|
|||
preexisting bytecode file should occur only if the file is owned by
|
||||
the current user or root. (Does this matter on Windows?)
|
||||
|
||||
- The interaction of this PEP with import hooks has not been
|
||||
considered yet. In fact, the best way to implement this idea might
|
||||
be as an import hook. See PEP 302. [5]_
|
||||
|
||||
|
||||
Examples
|
||||
========
|
||||
|
@ -275,6 +279,9 @@ References
|
|||
.. [4] python-dev thread, Parallel pyc construction, Dubois
|
||||
(http://mail.python.org/pipermail/python-dev/2003-January/032060.html)
|
||||
|
||||
.. [5] PEP 302, New Import Hooks, van Rossum and Moore
|
||||
(http://www.python.org/dev/peps/pep-0302.html)
|
||||
|
||||
|
||||
Copyright
|
||||
=========
|
||||
|
|
Loading…
Reference in New Issue