Conversation
Run `black` across the backend/ directory to standardise formatting. This is an automated formatting-only change with no structural logic changes.
Author
|
@jmplaza could you take a look when you get a chance? This formats the Python backend with black for consistent style. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #444.
Runs
blackacross thebackend/directory to standardise formattingin line with PEP 8 / the issue description.
What's included
backend/.black --check backend/(24 files left unchanged) andpython3 -m py_compileon every touched file. No structural or logic changes.Notes
.blackconfig exists in the repo, so this uses the default(88-col, double quotes). Happy to switch the line length/settings if
the maintainers prefer a project config.
outputs.pyis included since it's part ofbackend/; a separate fixPR (for Outputs.share() fails on Windows: shape/dim wires are sized as int32 but always read as int64 #483/Outputs.share() under-allocates the data wire whenever check_type() promotes the dtype #484) touches the same file — whichever merges first, the
other may need a trivial rebase.