I absolutely agree that it would be a shame to let Pygres die. I use it for everything to do with Postgres and Python except django development - for the obvious reason.
Paul HIde On 9 March 2011 13:56, D'Arcy J.M. Cain <[email protected]> wrote: > On Sun, 06 Mar 2011 19:35:30 +0100 > Christoph Zwerschke <[email protected]> wrote: > > That's true, Postgres arrays have never been supported by Pygres, > > probably because they were pretty restricted anyway so hardly anybody > > was using them (maybe they have become more useful in newer Postgres > > versions, though). > > I used arrays way back when I first started using Postgres but gave > them up pretty quick. I found that whenever I used an array, a small > table was a lot simpler and more flexible. > > > However, motivation to work on Pygres dwindled strongly after psycopg2 > > changed its license and has become so much better, so there seems to be > > no real need for Pygres any more these days. E.g. I think psycopg2 > > already supports arrays. > > > > But resuming Pygres development is still on my todolist, it would be a > > shame to let Pygres die. Don't know what others think (D'Arcy?). > > Agreed. I have been a bit busy lately but there are two items at the > top of my personal list; Support Python 3 and make the classic > interface pur Python so that it can work with any other interface such > as psycopg2 and even non PostgreSQL DB-API modules. > > -- > D'Arcy J.M. Cain > PyGreSQL Development Group > http://www.PyGreSQL.org > _______________________________________________ > PyGreSQL mailing list > [email protected] > http://mailman.vex.net/mailman/listinfo/pygresql >
_______________________________________________ PyGreSQL mailing list [email protected] http://mailman.vex.net/mailman/listinfo/pygresql
