-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
M.-A. Lemburg wrote: | Gerhard Haering wrote: | |> My point is to include a usable DB-API 2.0 implementation that people |> can use as a starting point when developing applications that need a |> relational database. Other languages do the same btw. Java (win32?) |> includes a JDBC driver or ODBC, and PHP5 includes a SQLite module. | | | Note that JDBC and ODBC are database driver interfaces much like | the Python DB API, not database drivers. You still need to add | a JDBC or ODBC driver in order to talk to the database backend | of your choice (just like you have to do with the DB API). | | Adding an SQLite interface goes beyond that since it is a | database driver for a specific database backend. | | If you are just after a "usable database driver", then I have to | agree with Skip: any of the other available drivers would fit in | just as well. Please clarify this. |
I doubt that anything except Gadfly or SQLite could be built from a Python source distribution. The others, such as PostgreSQL or Oracle drivers, would require a chunk of the database distribution or licences to build and would lock you using a particular release of the database backend.
The other product suitable for inclusion would be SQLRelay if its maintainers and its release cycle agree.
If I remember correctly, Gadfly would have been in 2.4 if anybody had been able to commit to the long term maintenance of it, so I thought the 'should we' question had already been answered.