-
Notifications
You must be signed in to change notification settings - Fork 62
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
Adopt Black for Python. #1906
Adopt Black for Python. #1906
Conversation
Building docs is not part of our tests, but relies on much of our Python code. Can you confirm it builds fine? |
They do. All the literal include lines are in jeopardy though. As discussed elsewhere, this should be merged in close |
What about an |
We can do that, but -- I assume -- not before merging this, since we need to commit IDs? |
Yes, that's how I've always done it 🤷♀️ |
Then I can only say thank you for the hint, will do ;) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with black 👍 This makes the '"label"'
syntax slightly weirder
How so? Black doesn't seem to touch those. Maybe just maybe, we can |
- Mention arbor-contrib in a few relevant places - Correct some fallout from arbor-sim#1904 - A new hardware and profiling tutorial, and covers things moved out of other examples in arbor-sim#1904 - Various other documentation fixes
Add black formatter