Clarify that hybrid namespace packages don't have dynamic path computation.
This commit is contained in:
parent
3e06b46245
commit
56fc179367
|
@ -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
|
||||
to be migrated to this PEP at once, ``extend_path()`` will be modified
|
||||
to also recognize PEP 420 namespace packages. This will allow some
|
||||
portions of a namespace to be legacty portions while others are
|
||||
migrated to PEP 420.
|
||||
portions of a namespace to be legacy portions while others are
|
||||
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
|
||||
|
|
Loading…
Reference in New Issue