[Python-Dev] PEP 2: Procedure for Adding New Modules
Martijn Faassen
faassen@vet.uu.nl
Thu, 14 Mar 2002 23:59:16 +0100
Hi there,
My first post here. Hello everybody. You may have heard of me. :)
Many moons ago I was in a comp.lang.python discussion where extensions
to the standard library came up. Comments were that it was developed
slowly compared to the core language (this was in 2.2 development times),
and Tim Peters said things like the following:
> What is a hangup is that people also want stuff the current group of core
> developers has no competence (and/or sometimes interest) to write. Like SSL
> support on Windows, or IPv6 support, etc. Expert-level work in a field
> requires experts in that field to contribute.
> We also need a plan to keep
> their stuff running after they go away again, the lack of which is one
> strong reason Guido resists adding stuff to the library.
I said the following:
>> perhaps it would be good to set up an semi-formal group that *does*
>> treat this as their 'core business' (manage core library development
>> and perhaps even independent releases) A library-SIG, perhaps?
And Tim said:
> Start by adding some meat to PEP 2.
And so I said I'd do some work on it. Contacted Eric Raymond who'd written
the one line of it that was there then, and got his permission to work on
it. And I wrote most of it. Got various comments on it on comp.lang.python.
And then it languished until this week, when I dug it up again, and
Barry posted it to the list of PEPs as a draft. So here it is:
http://python.sourceforge.net/peps/pep-0002.html
Is this going in the right direction? Any things I should change?
Note that the PEP does not talk so much about the technical issues.
At the time there was some work done on a separate PEP describing some
of those, but that one seems to have languished as well. This is an
early version of that, in case there's interest in reviving that effort:
http://groups.google.com/groups?selm=mailman.994034642.25601.python-list%40python.org&rnum=1
Regards,
Martijn