-
Notifications
You must be signed in to change notification settings - Fork 277
Python code format #1954
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
Python code format #1954
Conversation
Ideally, we should add this to CI so that |
Yes, that would be nice I think. let me see how can I link gradlew with ruff or is there is other alternatives that we can use. |
Thanks for review @eric-maynard. I will open another one once I have the automation ready based on above discussion. |
@MonkeyCanCode what exactly did you run here btw? I still see conflicts/changes on #1912 after running |
For the above, I am using
I will look into on how we can automate this tomorrow. |
@eric-maynard sample PR is ready: #1986 let me know what you think. Thanks. |
@eric-maynard after #1995 is merged, u can just run |
Formatted python code base with ruff (https://docs.astral.sh/ruff/). If there is no concern with this route, should we consider use ruff for code formatting and reject PRs that doesn't follow the format (same mechanism is there for current java code base via RAT). Ruff is under MIT license.