News for hackers. Stuff that matters.
Re:Psycopg3: A First Report by sdrothrock on Tuesday March 31, 2020 @11:35PM (#22745391)
I read this and my first question was "Why?"

He has a previous post titled "Thinking psycopg3" that shed some light on the issue: https://www.varrazzo.com/blog/2020/03/06/thinking-psycopg3/

- Query parameters adaption

- Context managers and transactions

- Optional C module (i.e. reduce requirements)

- Async from the ground up

- Resolve other outstanding issues

Reading that post first went a long way toward giving me some context to understand this one.

Re:Psycopg3: A First Report by OldTechSucks on Wednesday April 01, 2020 @07:09AM (#22747518)
Just use SqlAlchemy :)) the post doesn't make any sense
Re:Psycopg3: A First Report by Spiritus on Wednesday April 01, 2020 @09:10AM (#22748151)
What are you talking about? What do you think SQLAlchemy uses as a Postgres driver?

Sure, there's some alternatives. But 99% use psycopg2.