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

Clarify that hybrid namespace packages don't have dynamic path computation.

This commit is contained in:
Eric V. Smith 2012-05-16 09:53:58 -04:00
parent 3e06b46245
commit 56fc179367
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
pep-0420.txt
View File

@ -245,8 +245,10 @@ used by legacy portions to create namespace packages. Because it is
likely not practical for all existing portions of a namespace package likely not practical for all existing portions of a namespace package
to be migrated to this PEP at once, ``extend_path()`` will be modified to be migrated to this PEP at once, ``extend_path()`` will be modified
to also recognize PEP 420 namespace packages. This will allow some to also recognize PEP 420 namespace packages. This will allow some
portions of a namespace to be legacty portions while others are portions of a namespace to be legacy portions while others are
migrated to PEP 420. migrated to PEP 420. These hybrid namespace packages will not have
the dynamic path computation that normal namespace packages have,
since ``extend_path()`` never provided this functionality in the past.
Packaging Implications Packaging Implications