Psycopg 3 supports both sync and async code. Starting from release 3.2, the sync side is automatically generated from the async counterpart. This article explains how it's done, and the workflow used for the initial conversion to autogenerated code and for the regular maintenance.
As someone who is trying to make a living out of free software, I would love to see this project succeeding.
The other remotely similar service, Tidelift, has unacceptable terms and conditions: for the compensation they decide "at [their] sole discretion", "[i]f you do not satisfactorily provide the Services, Tidelift may, at its option and without limitation, (a) require you to immediately re-perform the applicable Service at no additional charge; and/or (b) reduce the fees paid, or due to be paid, to you for the applicable Service in an amount commensurate with the cost to the Subscriber to cover the breach and/or the cost to Tidelift to assist its Subscriber with covering the breach." Quotes taken from the May 2022 "Lifter Agreement", which I was asked to sign for the monthly equivalent of what a professional charges for 30 minutes of work.
I hope that Ringer will prove a real contact point between Free Software professionals and professional users.
This is interesting, thank you for pointing it out. Worth looking if the problems can be fixed the same way in both the adapter (and probably everything else using server-side binding).
There is a mechanism to ensure that there is no unexpected regression. Exposing the PSYCOPG_IMPL env var a program can make sure to obtain a specific implementation and import fails if it's not available. https://www.psycopg.org/psycopg3/docs/api/pq.html