Thread: postgres library in Python core
Over on the python-ideas list, GvR indicated interest in someone looking into including a postgres module (and mysql) inthe stdlib. http://mail.python.org/pipermail/python-ideas/2013-March/019874.html Quoting from there: > The number one question to ask about candidates for standard library > inclusion is "Does it make sense for this module to receive new > features only once every 18-24 months, and only when you upgrade to a > new version of Python?". Interfaces to specific external services > (including databases) almost never pass that test. Also mentioned there was that inclusion would need a commitment for maintenance and backward compatibility. Do you think psycopg can fit that bill? Is there interest in pursuing it? Ryan Hiebert
On 03/07/2013 07:42 PM, ryan@ryanhiebert.com wrote: > Over on the python-ideas list, GvR indicated interest in someone looking into including a postgres module (and mysql) inthe stdlib. > > http://mail.python.org/pipermail/python-ideas/2013-March/019874.html > > Quoting from there: > >> The number one question to ask about candidates for standard library >> inclusion is "Does it make sense for this module to receive new >> features only once every 18-24 months, and only when you upgrade to a >> new version of Python?". Interfaces to specific external services >> (including databases) almost never pass that test. > > Also mentioned there was that inclusion would need a commitment for maintenance and backward compatibility. > > Do you think psycopg can fit that bill? Is there interest in pursuing it? Given that there is a major release of Postgres about once a year I am not sure how the new features only 18-24 months would pan out? As much as I would like to see psycopg2/Postgres be one of the batteries included, I am not sure that is possible. I see a lot of explaining to people why the built in driver does not work with new features. > > Ryan Hiebert > -- Adrian Klaver adrian.klaver@gmail.com
On Fri, Mar 8, 2013 at 3:42 AM, <ryan@ryanhiebert.com> wrote: > Over on the python-ideas list, GvR indicated interest in someone looking into including a postgres module (and mysql) inthe stdlib. Here is the laundry list to have a module added to the stdlib: http://docs.python.org/devguide/stdlibchanges.html I've pondered on it in the past for another project of mine (setproctitle) and the conclusion is that 1) it would effectively stop the library development and 2) I wouldn't enjoy the friendly fire. "Be prepared for extensive feedback and lots of discussion (not all of it positive)": I'm not, thank you very much. Psycopg also enjoys external dependencies (the libpq, and a postgres server for testing) and an opinionated license (LGPL) making it a non-starter if Python maintainers don't want to bloat their build system and their legal department. -- Daniele
On 08/03/2013 11:50, Daniele Varrazzo wrote: > On Fri, Mar 8, 2013 at 3:42 AM, <ryan@ryanhiebert.com> wrote: >> > Over on the python-ideas list, GvR indicated interest in someone looking into including a postgres module (and mysql)in the stdlib. > Here is the laundry list to have a module added to the stdlib: > http://docs.python.org/devguide/stdlibchanges.html > > I've pondered on it in the past for another project of mine > (setproctitle) and the conclusion is that 1) it would effectively stop > the library development and 2) I wouldn't enjoy the friendly fire. "Be > prepared for extensive feedback and lots of discussion (not all of it > positive)": I'm not, thank you very much. > > Psycopg also enjoys external dependencies (the libpq, and a postgres > server for testing) and an opinionated license (LGPL) making it a > non-starter if Python maintainers don't want to bloat their build > system and their legal department. I just wanted to add while adding a module to the core Python lib feels good and warm I don't see any real advantage. I don't think core Python developers will flock to help and stdlibchanges.html is scary enough. So I am 100% with NOT including psycopg. federico