Re: postgres library in Python core

From: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
To: ryan(at)ryanhiebert(dot)com
Cc: psycopg(at)postgresql(dot)org
Subject: Re: postgres library in Python core
Date: 2013-03-08 03:54:21
Message-ID: 513960ED.2090504@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: psycopg

On 03/07/2013 07:42 PM, ryan(at)ryanhiebert(dot)com wrote:
> Over on the python-ideas list, GvR indicated interest in someone looking into including a postgres module (and mysql) in the 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(dot)klaver(at)gmail(dot)com

In response to

Browse psycopg by date

  From Date Subject
Next Message Daniele Varrazzo 2013-03-08 10:50:52 Re: postgres library in Python core
Previous Message ryan 2013-03-08 03:42:31 postgres library in Python core