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

Corrections from Guido.

This commit is contained in:
Eric V. Smith 2012-05-20 19:39:00 -04:00
parent 40dee2096f
commit 49d7dec285
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
pep-0420.txt
View File

@ -85,7 +85,7 @@ rejected, but the motivating use cases are still valid.
Rationale
=========
The current imperative approach to namespace packages has lead to
The current imperative approach to namespace packages has led to
multiple slightly-incompatible mechanisms for providing namespace
packages. For example, pkgutil supports ``*.pkg`` files; setuptools
doesn't. Likewise, setuptools supports inspecting zip files, and
@ -128,7 +128,9 @@ directory in the parent path:
imported and returned.
* If not, but ``<directory>/foo.{py,pyc,so,pyd}`` is found, a module
is imported and returned.
is imported and returned. The exact list of extension varies by
platform and whether the -O flag is specified. The list here is
representative.
* If not, but ``<directory>/foo`` is found and is a directory, it is
recorded and the scan continues with the next directory in the
@ -314,7 +316,8 @@ They are:
4. Implicit package directories will permanently entrench current
newbie-hostile behavior in ``__main__``.
Nick gave a detailed response [5]_, which is summarized here:
Nick later gave a detailed response to his own objections[5]_, which
is summarized here:
1. The practicality of this PEP wins over other proposals and the
status quo.