Am 11.07.2010 20:58 schrieb D'Arcy J.M. Cain:
It is still http://trac.pygresql.org:8000/trac. Problem was that I had
to change the name of the PyGreSQL user as it conflicted with the
mailing list and I forgot to restart the trac server. Check it now.
As for SVN, the URI on the page works for me. What do you get? The
web interface works as well.
Ok, it works now, but only the tracker and not the SVN repository
integration. There should be a button "browse source". Without the SVN
integration, Trac is not much fun.
I can't do an SVN checkout because I cannot log in to your server any
more. It seems my authorized_keys file or my whole account "cito"
doesn't exist any more on the server.
That seems like a good approach. It's almost like Approach 3 except
that it includes 2.6 and 2.7 in the new code branch. Should we drop
2.3 support in 4.1 anyway? I personally don't have a test environmemnt
for it any more. Does anyone else?
I'm all for dropping 2.3 support unless somebody comes up with very good
reasons for keeping it. Maybe not yet in 4.1, but in 5.x. We then don't
need to bother about missing decimals, sets or the like. Py 2.4 should
be supported, since it's still used by some current enterprise Linux
distributions.
Would 4.x become a bugfix only branch?
Yes, I would say so. Version 5.x would then be the first with Python 3
support via 2to3, and still support Py 2.4. But it could contain new
features and small API changes (I think some things need to be fixed,
e.g. concerning date type conversion).
-- Christoph
_______________________________________________
PyGreSQL mailing list
[email protected]
http://mailman.vex.net/mailman/listinfo/pygresql
