iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Change the wording for why the Mac modules should go.

This commit is contained in:
Brett Cannon 2008-03-19 21:00:47 +00:00
parent fa191901ac
commit 936e0f67eb
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
pep-3108.txt
View File

@ -368,11 +368,12 @@ for what the module is meant for.
Mac-specific modules Mac-specific modules
//////////////////// ////////////////////
Thanks to both Apple including Python with OS X and PyObjC_, The Mac-specific modules are mostly unmaintained (e.g., the bgen
the included Mac modules in Python are obsolete. tool used to auto-generate many of the modules has never been
Apple's Cocoa API will always be more up-to-date than Python's own updated to support UCS-4). It is also not Python's place to maintain
attempt at maintaining wrappers. Plus Apple can be expected to such a large amount of OS-specific modules. For modules that provide
include useful Mac-only modules that third-parties do not provide. a small amount of focused functionality (e.g., _winreg), that can be
considered reasonable.
* aepack * aepack