From: | Federico Di Gregorio <fog(at)dndg(dot)it> |
---|---|
To: | psycopg(at)postgresql(dot)org |
Subject: | Re: postgres library in Python core |
Date: | 2013-03-12 16:54:29 |
Message-ID: | 513F5DC5.7040608@dndg.it |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | psycopg |
On 08/03/2013 11:50, Daniele Varrazzo wrote:
> On Fri, Mar 8, 2013 at 3:42 AM, <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.
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Don Parris | 2013-03-13 00:47:26 | parameterized full text search problem |
Previous Message | Daniele Varrazzo | 2013-03-08 10:50:52 | Re: postgres library in Python core |