On Wed, 31 Oct 2012 13:01:01 +0100 Christoph Zwerschke <[email protected]> wrote:
> The last version officially supported Py 2.3-2.6 and Pg 7.4-8.4. I > saw you changed that to Py 2.5-2.7 and Pg 8.3-9.2 for v4.1. Yes, that cleaned up a trac item. > But there are still many places which make provisions for earlier > versions, and the checks and docstring in setup.py also still have > the old version ranges. I want to clean that up, but first we need to > decide, do we want to silently allow the old versions (just > undocumented, untested and unsupported), or do we want to check for > Py 2.5 in setup.py and remove all the code for supporting older > versions? My idea was to start cleaning up but not in an OCD way. Having the officially supported versions means that we can refactor as needed when we start working on new code. We don't actually have a way of testing against the matrix of all supported versions. Any ideas about that? > We also have ticket #20 that needs Py 2.5 and was originally planned > for 4.2. It would be nice to get that into 4.1 already then. Go for it. -- D'Arcy J.M. Cain PyGreSQL Development Group http://www.PyGreSQL.org IM:[email protected] _______________________________________________ PyGreSQL mailing list [email protected] https://mail.vex.net/mailman/listinfo.cgi/pygresql
