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

Defer PEP 395 until I make it compatible with PEP 420

This commit is contained in:
Nick Coghlan 2012-11-20 23:35:12 +10:00
parent fba6f8932b
commit 304bfb8c80
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
pep-0395.txt
View File

@ -3,11 +3,11 @@ Title: Qualified Names for Modules
Version: $Revision$ Version: $Revision$
Last-Modified: $Date$ Last-Modified: $Date$
Author: Nick Coghlan <ncoghlan@gmail.com> Author: Nick Coghlan <ncoghlan@gmail.com>
Status: Draft Status: Deferred
Type: Standards Track Type: Standards Track
Content-Type: text/x-rst Content-Type: text/x-rst
Created: 4-Mar-2011 Created: 4-Mar-2011
Python-Version: 3.3 Python-Version: 3.4
Post-History: 5-Mar-2011, 19-Nov-2011 Post-History: 5-Mar-2011, 19-Nov-2011
@ -24,6 +24,11 @@ It builds on the "Qualified Name" concept defined in PEP 3155.
Relationship with Other PEPs Relationship with Other PEPs
---------------------------- ----------------------------
Most significantly, this PEP is currently deferred as it requires
significant changes in order to be made compatible with the removal
of mandatory __init__.py files in PEP 420 (which has been implemented
and released in Python 3.3).
This PEP builds on the "qualified name" concept introduced by PEP 3155, and This PEP builds on the "qualified name" concept introduced by PEP 3155, and
also shares in that PEP's aim of fixing some ugly corner cases when dealing also shares in that PEP's aim of fixing some ugly corner cases when dealing
with serialisation of arbitrary functions and classes. with serialisation of arbitrary functions and classes.
@ -32,11 +37,6 @@ It also builds on PEP 366, which took initial tentative steps towards making
explicit relative imports from the main module work correctly in at least explicit relative imports from the main module work correctly in at least
*some* circumstances. *some* circumstances.
This PEP is also affected by the two competing "namespace package" PEPs
(PEP 382 and PEP 402). This PEP would require some minor adjustments to
accommodate PEP 382, but has some critical incompatibilities with respect to
the implicit namespace package mechanism proposed in PEP 402.
Finally, PEP 328 eliminated implicit relative imports from imported modules. Finally, PEP 328 eliminated implicit relative imports from imported modules.
This PEP proposes that the de facto implicit relative imports from main This PEP proposes that the de facto implicit relative imports from main
modules that are provided by the current initialisation behaviour for modules that are provided by the current initialisation behaviour for