protobuf

Protocol Buffers - Google's data interchange format (grpc依赖) https://developers.google.com/protocol-buffers/

Tag: Branch: Tree: 937b56f57b

Nipunn Koorapati 937b56f57b Match service argument names to abstract interface (#9418 ) The base class/documentation suggest that the argument names are `self` and `done`, while the runtime used argument names `srvc` and `callback`. `mypy.stubtest` was able to identify this - as it compares the types (autogenerated by [`mypy-protobuf`](https://github.com/dropbox/mypy-protobuf/)) to the actual code generated by protoc at runtime. Since the stubs assume the generated code matches the abstract interface in service.py - it saw these differences.	3 years ago
..
protobuf	Match service argument names to abstract interface (#9418 )	3 years ago
__init__.py	Auxillary -> Auxiliary	5 years ago

Match service argument names to abstract interface (#9418 )

The base class/documentation suggest that the argument
names are `self` and `done`, while the runtime used
argument names `srvc` and `callback`.

`mypy.stubtest` was able to identify this - as it compares
the types (autogenerated by
[`mypy-protobuf`](https://github.com/dropbox/mypy-protobuf/))
to the actual code generated by protoc at runtime.

Since the stubs assume the generated code matches the abstract
interface in service.py - it saw these differences.

3 years ago

protobuf

Match service argument names to abstract interface (#9418 )

3 years ago

__init__.py

Auxillary -> Auxiliary

5 years ago