Normalize 'file system'.
This commit is contained in:
parent
c0fe0bbee5
commit
40dee2096f
|
@ -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
|
||||
the namespace package. However, Linux distribution vendors (amongst
|
||||
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*
|
||||
file on the target system - something that is not allowed by many
|
||||
package managers. Allowing implicit namespace packages means that the
|
||||
|
@ -308,7 +308,7 @@ They are:
|
|||
2. Implicit package directories pose awkward backwards compatibility
|
||||
challenges.
|
||||
|
||||
3. Implicit package directories introduce ambiguity into filesystem
|
||||
3. Implicit package directories introduce ambiguity into file system
|
||||
layouts.
|
||||
|
||||
4. Implicit package directories will permanently entrench current
|
||||
|
|
Loading…
Reference in New Issue