Slight clarifications about packaging.

This commit is contained in:
Eric V. Smith 2012-04-26 08:30:19 -04:00
parent 61b2840d94
commit 45bbfe1672
1 changed files with 4 additions and 4 deletions

View File

@ -199,9 +199,9 @@ Packaging Implications
====================== ======================
Multiple portions of a namespace package can be installed into the Multiple portions of a namespace package can be installed into the
same location, or into separate locations. For this section, suppose same directory, or into separate directories. For this section,
there are two portions which define "foo.bar" and "foo.baz". "foo" suppose there are two portions which define "foo.bar" and "foo.baz".
itself is a namespace package. "foo" itself is a namespace package.
If these are installed in the same location, a single directory "foo" If these are installed in the same location, a single directory "foo"
would be in a directory that is on ``sys.path``. Inside "foo" would would be in a directory that is on ``sys.path``. Inside "foo" would
@ -215,7 +215,7 @@ If the portions are installed in different locations, two different
"foo" directories would be in directories that are on ``sys.path``. "foo" directories would be in directories that are on ``sys.path``.
"foo/bar" would be in one of these sys.path entries, and "foo/baz" "foo/bar" would be in one of these sys.path entries, and "foo/baz"
would be in the other. Upon removal of "foo.bar", the "foo/bar" and would be in the other. Upon removal of "foo.bar", the "foo/bar" and
corresonding "foo" directories can be removed. corresonding "foo" directories can be completely removed.
Note that even if they are installed in the same directory, "foo.bar" Note that even if they are installed in the same directory, "foo.bar"
and "foo.baz" would not have any files in common. and "foo.baz" would not have any files in common.