-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
[CI] Migrate from YAPF to Black #21311
Comments
This was referenced Jan 1, 2022
Closed
6 tasks
pcmoritz
pushed a commit
that referenced
this issue
Jan 30, 2022
This was referenced Jan 30, 2022
Closed
Merged
This was referenced Jan 30, 2022
Closed
Closed
Closed
dmatrix
pushed a commit
to dmatrix/ray
that referenced
this issue
Jan 30, 2022
See ray-project#21316 and ray-project#21311 for the motivation behind these changes.
This is now finished, right? Thanks a lot for driving this @bveeramani ! |
There's one last minor PR #21984, but otherwise we're done! |
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview
The Ray Team has decided to format the Ray Python code with Black. This means that going forward, changes to Python code must adhere to the Black code style.
We'll be updating
./scripts/format.sh
, so if you're a contributor, your workflow shouldn't change.Motivation
We're switching to Black because:
For more information about the motivation behind this change, read the full proposal.
Implementation Plan
We're planning on rolling out the changes in three phases.
Phase One:
format.sh
to support the Black code style #21312multi_agent_env.py
#21314test_resource_demand_scheduler.py
#21313Phase Two:
Phase Three:
format.sh
#21319Timeline
1/151/29The text was updated successfully, but these errors were encountered: