Antithesis
I haven’t tried it yet, but assuming that I can make easy use of pg8000, a PostgreSQL that throws out c-based bindings and speaking postgresql-ish in native python, then it’s an example of the anti-thesis of “dragon tea”. It doesn’t appear to require hunting down obscure dependencies, it doesn’t require that you build ten other equally obscure things before you can use it, and if it delivers what it promises it will make developer’s lives much easier.I speak out of self-interest. I’m writing a PostgreSQL “utility belt” module that can serve as the data model layer for unique PostgreSQL systems administration/development applications. I’ve been fretting for a little while about requiring people to go through the hoops of installing psycopg2, which is a pain in the butt to install and also has some documentation/finding-on-the-internet issues.A completely self-contained python interface to PostgreSQL that completely bypasses libpq shennanigans would make the lives of developers who’d want to use my stuff that much easier. And making developer’s lives easier and bringing in the newbie programmers is a winning strategy. Much more of a winning strategy than catering to the few elites and their diatribes about performance hits taken by natively doing stuff in an interpreted language.Scripting languages are supposed to be slow; it’s called an engineering tradeoff. If you didn’t want it slower, you’d bypass the scripting language and do it in C and accept the tradeoff of performance for slower development time.Just my two. When the PostgreSQL utility belt is ready, I’ll probably post it here, or something.