Modules for inclusion in standard library?

Gregory Piñero gregpinero at
Wed Jun 29 21:04:05 CEST 2005

While that policy does make sense, I think a database program falls
somewhere in between an OS and an everyday third party program.  For
web developers, the database might as well be the OS.  I use the
database to store everything in my web app.  That way I can just worry
about 1 place to access information and not have to fool with files
and other OS issues.

So I humbly suggest the policy should be :

Python will not include interface code for third party programs which
are not part of an operating system or database system.

But I have no experience in designing world class programming
langauges so forgive me if I am too bold.


On 6/29/05, Rocco Moretti <roccomoretti at> wrote:
> Paul Rubin wrote:
> > Gregory Piñero <gregpinero at > writes:
> >
> >>I'd like to see some database API's to the most common databases
> >>included.
> >
> > Yes, certainly, this is a serious deficiency with Python.
> Except that (please correct me if I'm wrong) there is somewhat of a
> policy for not including interface code for third party programs which
> are not part of the operating system. (I.e. the modules in the standard
> libary should all be usable for anyone with a default OS + Python install.)
> A notable exception is the dbm modules, but I seem to recall hearing
> that the official position is that it was a mistake. (Now only kept for
> backward compatability.)
> --

More information about the Python-list mailing list