-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Bugfix: grpc python code generation location and file suffix #8359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugfix: grpc python code generation location and file suffix #8359
Conversation
7519c47 to
95c0ab2
Compare
|
Can this be merged @dbaileychess or does it need something else? |
|
Any update if this can be merged? @dbaileychess @anton-bobukh |
4aad523 to
e69f52b
Compare
e69f52b to
d1fabd4
Compare
|
Rebased to master any chance this can be merged @dbaileychess @anton-bobukh as this still breaks imports in python |
d1fabd4 to
4034a5d
Compare
|
rebased again |
4034a5d to
8e8cf3a
Compare
Having filenames with . like `file.fb.grcp` is not great for Python. Since dots are used for namespaces. Replacing all of them with _ eg suffix `foo.bar.baz` will become `foo_bar_baz`. Restoring the previous default `_fb` suffix.
This fixes a regression introduced with: fb9afba And generates the grpc file in the namespace folder again.
8e8cf3a to
e8dc507
Compare
|
@aardappel or @dbaileychess any chance this can also be merged to fix the regression after this was merged now #8500 |
|
CI issues seem unrelated |
|
Thanks :) |
|
Thank you ✨ good to see that flatbuffers is still maintained |
Follow up from #8356.
This addresses the regression for the location where the
grpcfile is generated andchanges the default suffix back to
_fbagain instead of.fb.(See commit messages for more details).