DNL: python: enable gazelle support #24
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a draft PR that enables gazelle support in the repo for python files, but unfortunately I ran into lots of problems around:
file
generation mode if there is aif __name__ == "__main__"
in a file not named__main__.py
# gazelle:python_*_naming_convention
directive is set__test__.py
All in all this seems nice to have, but enforces too many constraints around python development that don't fit in with the way I want python dev to work in this template. I'm uploading this in case anyone wants to pick it up and run with it or in case I want to follow up on it later, but in the meantime gazelle+python is dead in the water for this project