iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add reference to c.l.p discussion of bundling scripts as part of a package

This commit is contained in:
Nick Coghlan 2007-07-04 12:26:46 +00:00
parent a6928ec6ff
commit b97dfc0f1f
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
pep-0366.txt
View File

@ -18,7 +18,9 @@ This PEP proposes a backwards compatible mechanism that permits
the use of explicit relative imports from executable modules within the use of explicit relative imports from executable modules within
packages. Such imports currently fail due to an awkward interaction packages. Such imports currently fail due to an awkward interaction
between PEP 328 and PEP 338 - this behaviour is the subject of at between PEP 328 and PEP 338 - this behaviour is the subject of at
least one open SF bug report (#1510172)[1]. least one open SF bug report (#1510172)[1], and has lead to at least
a few queries on comp.lang.python (such as Alan Isaac's question in
[2]).
With the proposed mechanism, relative imports will work automatically With the proposed mechanism, relative imports will work automatically
if the module is executed using the ``-m`` switch. A small amount of if the module is executed using the ``-m`` switch. A small amount of
@ -173,6 +175,9 @@ References
.. [2] Guido's rejection of PEP 3122 .. [2] Guido's rejection of PEP 3122
(http://mail.python.org/pipermail/python-3000/2007-April/006793.html) (http://mail.python.org/pipermail/python-3000/2007-April/006793.html)
.. [3] c.l.p. question about modules and relative imports
(http://groups.google.com/group/comp.lang.python/browse_thread/thread/c44c769a72ca69fa/)
Copyright Copyright
========= =========