Let me add my "Hear hear!" to that, as well. Have more than one choice at any point in an software ecosystem usually leads to both choices getting better. Watching the tickets and commits fly by, with design notes and decisions documented, makes me want to use this as an example is a software development class, somewhere.
Kudos! Ross /me wonders just how deep a refactor Django would need to support PyGreSQL On Tue, Feb 09, 2016 at 08:09:57PM +0000, Davis, Sean (NIH/NCI) [E] wrote: > Usually a pretty quiet list, but I couldn’t let this one go by. Iit has been > fun watching development efforts over the past few weeks. Thanks for the > continued nice work! > > Sean > > > On Feb 9, 2016, at 3:05 PM, Christoph Zwerschke <[email protected]> wrote: > > > > Today I've closed the last open ticket for 5.0: SQLALchemy support. The > > complete SQLAlchemy test suite now works against a postgresql+pygresql > > database URL, with Python 2 and Python 3, in addition to our own test suite > > which has become pretty extensive. This makes me quite confident regarding > > 5.0. This is certainly the best PyGreSQL ever. The dialect for PyGreSQL > > will be integrated in the upcoming SQLAlchemy 1.1 version. > > > > -- Christoph > > _______________________________________________ > > PyGreSQL mailing list > > [email protected] > > https://mail.vex.net/mailman/listinfo.cgi/pygresql > > _______________________________________________ > PyGreSQL mailing list > [email protected] > https://mail.vex.net/mailman/listinfo.cgi/pygresql -- Ross Reedstrom, Ph.D. [email protected] Systems Engineer & Admin, Research Scientist phone: 713-348-6166 Connexions http://cnx.org fax: 713-348-3665 Rice University MS-375, Houston, TX 77005 GPG Key fingerprint = F023 82C8 9B0E 2CC6 0D8E F888 D3AE 810E 88F0 BEDE _______________________________________________ PyGreSQL mailing list [email protected] https://mail.vex.net/mailman/listinfo.cgi/pygresql
