> Next step would be someone to pick the preliminary work up and push it forward.
I guess I thought the "preliminary work" was already done. There's a driver written, and a PR for a django backend. I'd asked [Daniel Varrazzo](https://github.com/dvarrazzo/django-psycopg3-backend/issues/6) if he was planning to do it, and he said: > I am not actively working with the Django developers: I wrote the driver and the first iteration of the backend but I left the ball in their field. I give them feedback when they ask, but I'm not doing more than this. > You should hear from the Django project about their plans. On Wednesday, May 11, 2022 at 8:04:20 AM UTC-4 carlton...@gmail.com wrote: > On Wed, 11 May 2022 at 13:53, thinkwel...@gmail.com <thinkwel...@gmail.com> > wrote: > >> Will the psycopg3 backend <https://code.djangoproject.com/ticket/33308> >> land in time for the 4.1 release? I'm looking forward to it, as it should >> support PyPy much better than psycopg2 does. >> > > No. It's not been worked on recently as far as I know. Next step would be > someone to pick the preliminary work up and push it forward. (A major > feature like that isn't something we'd add to the roster the week before > the feature freeze: we'd likely see it coming the whole release cycle.) > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/f4d15ee7-faee-4841-8518-970ab6a2c1a7n%40googlegroups.com.
