mirror of
https://github.com/protocolbuffers/protobuf
synced 2026-08-26 02:23:14 -04:00
937b56f57b
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. |
||
|---|---|---|
| .. | ||
| compiler | ||
| internal | ||
| pyext | ||
| util | ||
| __init__.py | ||
| descriptor.py | ||
| descriptor_database.py | ||
| descriptor_pool.py | ||
| json_format.py | ||
| message.py | ||
| message_factory.py | ||
| proto_api.h | ||
| proto_builder.py | ||
| python_protobuf.h | ||
| reflection.py | ||
| service.py | ||
| service_reflection.py | ||
| symbol_database.py | ||
| text_encoding.py | ||
| text_format.py | ||