L97: Python: Setuptools entrypoint for generating file #290
Conversation
|
|
L96-python-setuptools-plugin.md
Outdated
| the same `main()` function used by the `grpc_tools.protoc` CLI. A [tool table][tool_table] within the | ||
| file `pyproject.toml` will be used to accept configuration parameters. This will add a dependency on | ||
| tomli for now, but this will [not be needed][pep_680] starting in Python 3.11. | ||
|
|
There was a problem hiding this comment.
Optional: The import path generated by grpc_tools.protoc can be counterintuitive grpc/grpc#9575. In the config file, we might want to provide the flexibility to: 1. set the work directory; 2. the "prefixes_to_filter" argument.
CC @gnossen , if you got a second, can you help about how to use "prefixes_to_filter" in our generator?
There was a problem hiding this comment.
prefixes_to_filter is currently not available in grpcio-tools, only in the Bazel rules, so I think it's okay to leave it out of this proposal, at least initially. Regardless, this is the best reference on usage.
plannigan
force-pushed
the
L96-python-setuptools-plugin
branch
from
b571cc7
to
29baceb
Compare
plannigan
changed the title
|
Number had to be updated because #240 was merged using L96 after this PR was initially created. |
L97-python-setuptools-plugin.md
Outdated
|
|
||
| `grpcio-tools` will register a new entrypoint function to respond to the `setuptools.file_finders` | ||
| hook. This hook will generate Python files based on the `.proto` files and tell `setuptools where | ||
| they were generated. |
There was a problem hiding this comment.
Can we update the example to show how the proto to Python generation should work?
Add some more specifics on how the end user would enable to functionality
plannigan
force-pushed
the
L96-python-setuptools-plugin
branch
from
14e7d71
to
6ec57ba
Compare
No description provided.