Skip site navigation (1) Skip section navigation (2)

Re: Confusion over Python drivers {license}

From: Greg Smith <greg(at)2ndquadrant(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: Kevin Ar18 <kevinar18(at)hotmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Confusion over Python drivers {license}
Date: 2010-02-13 08:45:33
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Jeff Davis wrote:
> Keep in mind that backwards compatibility is not the only issue here;
> forwards compatibility matters as well*. A lot of the encoding issues I
> wrote up ( ) will
> probably be real bugs in a python3 application using a driver that
> doesn't understand encoding properly.

Sure, but the benefit of being the de-facto standard to some problem, 
because you're already supported by everybody, is that it's easier to 
attract the most help to move forward too.  The disclaimers on 
investments always read "past performance is not indicative of future 
results".  I don't think that's really true in the open-source project 
case.  Generally, I'd rather trust a project that's been keeping up with 
things for a long time already to continue to do so, particularly one 
that's built up a community around it already, rather than risk 
switching to one without a known good track record in that record. 

(Exercise for the reader: consider how what I just said applies in both 
a positive and negative way toward MySQL and its associated development 

Greg Smith    2ndQuadrant   Baltimore, MD
PostgreSQL Training, Services and Support

In response to

pgsql-hackers by date

Next:From: Tim BunceDate: 2010-02-13 10:17:55
Subject: Re: Package namespace and Safe init cleanup for plperl [PATCH]
Previous:From: Greg SmithDate: 2010-02-13 08:34:23
Subject: Re: Re: [COMMITTERS] pgsql: Remove old-style VACUUM FULL (which was known for a little while

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group