Change the wording for why the Mac modules should go.
This commit is contained in:
parent
fa191901ac
commit
936e0f67eb
11
pep-3108.txt
11
pep-3108.txt
|
@ -368,11 +368,12 @@ for what the module is meant for.
|
|||
Mac-specific modules
|
||||
////////////////////
|
||||
|
||||
Thanks to both Apple including Python with OS X and PyObjC_,
|
||||
the included Mac modules in Python are obsolete.
|
||||
Apple's Cocoa API will always be more up-to-date than Python's own
|
||||
attempt at maintaining wrappers. Plus Apple can be expected to
|
||||
include useful Mac-only modules that third-parties do not provide.
|
||||
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.
|
||||
|
||||
* aepack
|
||||
|
||||
|
|
Loading…
Reference in New Issue