-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add RFC 004-Python Implementation #71
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
❤️ Many, many thanks for writing this up, Matt! We've been a little swamped, but this hasn't fallen off our radar. |
@mattrobenolt is attempting to deploy a commit to the connectrpc Team on Vercel. A member of the Team first needs to authorize it. |
@mattrobenolt @akshayjshah @mattrobenolt |
This covers both client and server
Thank you for creating the POC. The Connect over HTTP/1.1 is exactly what I was looking for. I might be checking the async implementation if other things related to Connect work well. |
any progress on this? |
👋 So to clarify, @mattrobenolt and @i2y if someone wants to contribute code for this effort, would it be best at this point to do so at https://github.com/mattrobenolt/connect-python or at https://github.com/i2y/connecpy and how hard would it be to merge these into one effort? Even more specifically, if I dumped any missing code from one into the other, from which repo to which repo should I go? I mean, it would also be great if someone could just get paid to work on this at their day job, but I know how hard it is to justify to management investing work on critical behind-the-scenes support when it is indirect to more immediate results. Thanks for all the volunteer work so far! ❤️ |
No description provided.