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

Record response (by Nick) to Nick's initial objections. I hope I've summarized correctly.

This commit is contained in:
Eric V. Smith 2012-05-01 12:37:58 -04:00
parent 75374a6026
commit 99806cc364
1 changed files with 22 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
pep-0420.txt
View File

@ -188,21 +188,30 @@ ImportWarning would be raised.
Nick Coglan presented a list of his objections to this proposal [3]_. Nick Coglan presented a list of his objections to this proposal [3]_.
They are: They are:
* Implicit package directories go against the Zen of Python 1. Implicit package directories go against the Zen of Python.
* Implicit package directories pose awkward backwards compatibility 2. Implicit package directories pose awkward backwards compatibility
challenges challenges.
* Implicit package directories introduce ambiguity into filesystem 3. Implicit package directories introduce ambiguity into filesystem
layouts layouts.
* Implicit package directories will permanently entrench current 4. Implicit package directories will permanently entrench current
newbie-hostile behaviour in __main__ newbie-hostile behaviour in ``__main__``.
(These need to be addressed here.) Nick gave a detailed response [4]_, which is summarized here:
1. Practicality beats purity.
2. Minor backward compatibility issues are okay, as long as they are
properly documented.
3. This will be addressed in PEP 395.
4. This will also be addressed in PEP 395.
Phillip Eby asked about auto-updating of ``__path__``, instead of it Phillip Eby asked about auto-updating of ``__path__``, instead of it
being a simple list [4]_. It is the intent of this PEP to get the being a simple list [5]_. It is the intent of this PEP to get the
simplest possible solution working. It will be possible at a later simplest possible solution working. It will be possible at a later
date to add such features. Several possible ways to do so were date to add such features. Several possible ways to do so were
discussed in the referenced email thread. discussed in the referenced email thread.
@ -248,7 +257,10 @@ References
.. [3] Nick Coglan's objection to the lack of marker files or directories .. [3] Nick Coglan's objection to the lack of marker files or directories
(http://mail.python.org/pipermail/import-sig/2012-March/000423.html) (http://mail.python.org/pipermail/import-sig/2012-March/000423.html)
.. [4] Phillip Eby's question about auto-updating __path__ .. [4] Nick Coglan's response to his initial objections
(http://mail.python.org/pipermail/import-sig/2012-April/000464.html)
.. [5] Phillip Eby's question about auto-updating __path__
(http://mail.python.org/pipermail/import-sig/2012-April/000468.html) (http://mail.python.org/pipermail/import-sig/2012-April/000468.html)
Copyright Copyright