Clarify some wording.
This commit is contained in:
parent
e3cf234347
commit
8bc8e44b23
12
pep-3108.txt
12
pep-3108.txt
|
@ -381,9 +381,7 @@ Mac-specific modules
|
|||
The Mac-specific modules are mostly unmaintained (e.g., the bgen
|
||||
tool used to auto-generate many of the modules has never been
|
||||
updated to support UCS-4). It is also not Python's place to maintain
|
||||
such a large amount of OS-specific modules. For modules that provide
|
||||
a small amount of focused functionality (e.g., _winreg), that can be
|
||||
considered reasonable.
|
||||
such a large amount of OS-specific modules.
|
||||
|
||||
* aepack
|
||||
|
||||
|
@ -737,9 +735,11 @@ Renaming of modules
|
|||
-------------------
|
||||
|
||||
For modules that are renamed, stub modules will be created with the
|
||||
original names and be kept in a package within the stdlib. The need
|
||||
to keep them within a package is to prevent naming conflicts
|
||||
with case-insensitive filesystems.
|
||||
original names and be kept in a directory within the stdlib (e.g. like
|
||||
lib-old was once used for). The need to keep the stub modules within
|
||||
a directory is to prevent naming conflicts with case-insensitive
|
||||
filesystems in those cases where nothing but the case of the module
|
||||
is changing.
|
||||
|
||||
These stub modules will import the module code based on the new
|
||||
naming. The same type of warning being raised by modules being
|
||||
|
|
Loading…
Reference in New Issue