This is a big release - the client now supports bidirectional streaming and the gRPC protocol. With this, connect-python is now a full-featured Connect implementation!

This is enabled by switching our HTTP client transport to pyqwest, a Python interface to the Rust HTTP client reqwest. This client supports all features of HTTP, allowing us to also support bidirectional streaming and gRPC (via HTTP trailers) in turn.

Keep in mind though that this is a very new project, built specifically to push connect-python forward. The underlying reqwest library has been in use for some time and should be battle-tested, but the Python wrapper is new - let us know if you run into any issues so we can fix them.

☢️ Breaking changes

• The HTTP transport for clients has been changed to pyqwest. If you created connect clients with default parameters, this will not need any further changes, but if passing a custom session, you will now need to pass a pyqwest client.

Before:

ctx = ssl.create_default_context(cafile="ca.path")
async with (
 httpx.AsyncClient(verify=ctx, http2=True) as session,
 GreeterClient("http://localhost", session=session) as client:
)

After:

async with (
 pyqwest.HTTPTransport(
 tls_ca_cert=Path("ca.path").read(), 
 http_version=pyqwest.HTTPVersion.HTTP2
 ) as transport,
 GreeterClient("http://localhost", http_client=pyqwest.Client(transport)
)

If you have unit tests using httpx.ASGITransport / httpx.WSGITransport, you also will need to migrate to pyqwest.testing.ASGITransport / pyqwest.testing.WSGITransport.

📈 Enhancements

• Add support for gRPC client protocol by @anuraaga in Add support for gRPC client protocol #80
• Migrate to pyqwest by @anuraaga in Migrate to pyqwest #88

🛠️ Bug fixes

• Avoid yielding messages on GeneratorExit in sync server by @anuraaga in Avoid yielding messages on GeneratorExit in sync server #90
• Drain request body in all error cases in WSGI by @anuraaga in Drain request body in all error cases in WSGI #94

Full Changelog: v0.7.1...v0.8.0