Two spaces after periods.
This commit is contained in:
parent
b15f631fa0
commit
31866ec3fb
|
@ -152,9 +152,9 @@ created as a package. The creation of the namespace package is not
|
|||
deferred until a sub-level import occurs.
|
||||
|
||||
A namespace package is not fundamentally different from a regular
|
||||
package. It is just a different way of creating packages. Once a
|
||||
package. It is just a different way of creating packages. Once a
|
||||
namespace package is created, there is no functional difference
|
||||
between it and a regular package. The only observable difference is
|
||||
between it and a regular package. The only observable difference is
|
||||
that the namespace package's ``__file__`` attribute will end with a
|
||||
path separator (typically a slash or backslash, depending on the
|
||||
platform).
|
||||
|
@ -219,7 +219,7 @@ If the portions are installed in different locations, two different
|
|||
"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"
|
||||
would be in the other. Upon removal of "foo.bar", the "foo/bar" and
|
||||
corresponding "foo" directories can be completely removed. But
|
||||
corresponding "foo" directories can be completely removed. But
|
||||
"foo/baz" and its corresponding "foo" directory cannot be removed.
|
||||
|
||||
It is also possible to have the "foo.bar" portion installed in a
|
||||
|
|
Loading…
Reference in New Issue