RobertCraigie
Deprecation of the Python client
Hello everyone, it's been long time coming but I'm officially stopping development of the Prisma Python Client.
This is for a couple of reasons:
- I originally built the client just for fun while I was a student, nowadays I don't have enough free time to properly maintain it.
- Prisma are rewriting their core from Rust to TypeScript. Unfortunately, adapting Prisma Client Python to this new architecture would require a ground up rewrite of our internals with significantly increased complexity as we would have to provide our own query interpreters and database drivers which is not something I'm interested in working on.
While it's certainly not impossible for community clients to exist in this new world, it is a lot more work. The Go, Rust, and Dart clients have similarly all been deprecated.
I greatly appreciate everyone who has supported the project over these last few years.
Thank you for all the hard work and dedication you've put into Prisma Client Python. Your contributions have been incredibly valuable, and your project has helped me (and many others) streamline our work. While it's sad to see it come to an end, I completely respect your decision and appreciate the effort you've put in over the years. Wishing you all the best in your future endeavors. Your work has truly made a difference.
Hi @RobertCraigie thanks for your work on this. Do you have any recommendations on alternatives we should move to for a python client ?
I do not have any personal recommendations. I've heard good things about SQLModel but haven't tried it enough myself.
Huge thanks for all your work on the Python client. I personally really enjoyed using it, and the effort you put into maintaining it has been very much appreciated. The experience of working with a shared, language-agnostic Prisma schema across Python, Go, and TypeScript has been a big win for our team.
It’s unfortunate that Prisma never officially supported the non-TypeScript clients, and with the recent direction of the project, it’s understandable that community efforts like this are becoming harder to sustain. That shift effectively limits Prisma to TypeScript, which means we’ll likely move away from it, as cross-language support was a major part of its value for us.
Thanks again for all the time and care you’ve put into this—we really appreciated being able to build on your work.
language-agnostic Prisma schema across Python, Go, and TypeScript has been a big win for our team.
Also feeling the same with @noamloewenstern . I love my Python project now able to sync database definition directly to my nextJS.
However @noamloewenstern , I am thinking, do you have any sample how Go can interact with Prisma schema? It is another topic of course, but you know..
