grpc-interceptor

What’s Changed

• Use TCP instead of UDS for tests. Fixes a compatibility issue with OpenTelemetry (#35) thanks @jenstroeger
• Run tests for Python 3.10 and 3.11 (#34) @d5h
• Drop 3.6 support; remove "safety" check in Github Actions (#28) @d5h
• Add missing word in docs (#24) @robertimpeysp
• Add missing "context" arg (#21) @metasyn

There are no functionality changes, just a bug fix, doc improvements, and some maintenance.

What’s Changed

Adds:

• AsyncServerInterceptor
• AsyncExceptionToStatusInterceptor
• Updated documentation (notably streaming and async)
• Async mode for existing tests where applicable
• More tests, especially around streaming

Requirement changes in order to support async:

• Python 3.6.1
• grpcio >= 1.32.0

Python 3.6.0 and grpcio < 1.32.0 won't get this, or future, updates. Async requires newer versions of these.

Notes:

• This doesn't add support for async client interceptors
• The read() / write() API for async streaming has tests, but mainly just that the interceptors can, in theory, operate with them. They require special handling (described in the docs), and getting access to the streaming request & response objects would require extra additional work by the end user (e.g., wrapping context).

What’s Changed

• Rebuild protobuf using protoc 3.19 (#18) @xiao-chen

What’s Changed

• Add tests with minimum versions of dependencies, and fix a few issues (#16)

This release doesn't add any new functionality, but adds tests with older versions of dependencies. In doing this, a couple issues were found and fixed.

There's one change which could conceivably break existing code, but only if people are depending on internals that weren't documented. Specifically, MethodName used to be a NamedTuple, which means it could be iterated over or compared to a tuple. Apparently, Python 3.6.0 doesn't allow @property attributes on a subclass of NamedTuple, so it's been changed to a normal class. There's no API changes, but if you had code that depended on the implementation detail of MethodName being a tuple, then it will break. If you are only using it as documented, then it should continue to work the same way.

What’s Changed

• Make ExceptionToStatusInterceptor more extensible (#12) @jeffsawatzky

What’s Changed

• ExceptionToStatusInterceptor: Fix streaming responses (#11) @craigds

What’s Changed

Added

• Run tests on Python 3.9 and default to that for linting, etc.

Fixed

• Raise UNIMPLEMENTED instead of UNKNOWN when no handler is found for a method (#9) @mahlberg

Changes:

• Client-side interceptors (thanks Michael Morgan!)

Changes:

• Add support for all streaming RPCs

Changes:

• Rename to ServerInterceptor
• Expose some imports from the top-level

Changes:

• Rename Interceptor to ServiceInterceptor
• Add status_on_unknown_exception to ExceptionToStatusInterceptor
• Add py.typed
• Allow protobuf version 4.0.x which is coming out soon and is backwards compatible
• Include testing in autodocs
• Turn on xdoctest Prevent autodoc from outputting default namedtuple docs

Changes in 0.9.0:

• Adds testing module
• Protobuf compatibility improvements
• Add some helper functions
• Improve test coverage

The release provides the following:

• An Interceptor base class, to make it easy to define your own service interceptors.
• An ExceptionToStatusInterceptor interceptor.