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

Normalize 'file system'.

This commit is contained in:
Eric V. Smith 2012-05-17 10:31:43 -04:00
parent c0fe0bbee5
commit 40dee2096f
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
pep-0420.txt
View File

@ -98,7 +98,7 @@ this configuration, it doesn't matter if multiple portions all provide
an ``__init__.py`` file, so long as each portion correctly initializes an ``__init__.py`` file, so long as each portion correctly initializes
the namespace package. However, Linux distribution vendors (amongst the namespace package. However, Linux distribution vendors (amongst
others) prefer to combine the separate portions and install them all others) prefer to combine the separate portions and install them all
into the *same* filesystem directory. This creates a potential for into the *same* file system directory. This creates a potential for
conflict, as the portions are now attempting to provide the *same* conflict, as the portions are now attempting to provide the *same*
file on the target system - something that is not allowed by many file on the target system - something that is not allowed by many
package managers. Allowing implicit namespace packages means that the package managers. Allowing implicit namespace packages means that the
@ -308,7 +308,7 @@ They are:
2. Implicit package directories pose awkward backwards compatibility 2. Implicit package directories pose awkward backwards compatibility
challenges. challenges.
3. Implicit package directories introduce ambiguity into filesystem 3. Implicit package directories introduce ambiguity into file system
layouts. layouts.
4. Implicit package directories will permanently entrench current 4. Implicit package directories will permanently entrench current