[Python-Dev] Adding library modules to the core (original) (raw)
Greg Ward gward@mems-exchange.org
Thu, 10 Aug 2000 08:38:02 -0400
- Previous message: [Python-Dev] Re: [Python-checkins] CVS: python/dist/src/Lib mailbox.py,1.20,1.21
- Next message: [Python-Dev] Adding library modules to the core
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[hmmm, this bounced 'cause the root partition on python.org was full... let's try again, shall we?]
On 07 August 2000, Eric S. Raymond said:
A few days ago I asked about the procedure for adding a module to the Python core library. I have a framework class for things like menu systems and symbolic debuggers I'd like to add.
Guido asked if this was similar to the TreeWidget class in IDLE. I investigated and discovered that it is not, and told him so. I am left with a couple of related questions:
Well, I just ploughed through this entire thread, and no one came up with an idea I've been toying with for a while: the Python Advanced Library.
This would be the place for well-known, useful, popular, tested, robust, stable, documented module collections that are just too big or too specialized to go in the core. Examples: PIL, mxDateTime, mxTextTools, mxODBC, ExtensionClass, ZODB, and anything else that I use in my daily work and wish that we didn't have maintain separate builds of. ;-)
Obviously this would be most useful as an RPM/Debian package/Windows installer/etc., so that non-developers could be told, "You need to install Python 1.6 and the Python Advanced Library 1.0 from ..." and that's it.
Thoughts? Candidates for admission? Proposed requirements for admission?
Greg
-- Greg Ward - software developer gward@mems-exchange.org MEMS Exchange / CNRI voice: +1-703-262-5376 Reston, Virginia, USA fax: +1-703-262-5367
- Previous message: [Python-Dev] Re: [Python-checkins] CVS: python/dist/src/Lib mailbox.py,1.20,1.21
- Next message: [Python-Dev] Adding library modules to the core
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]