Closed evalott100 closed 9 months ago
I'm on board with retroactively applying black
, but it would be best to do that in its own PR so that this PR is more reviewable as a unit.
I'm on board with retroactively applying
black
, but it would be best to do that in its own PR so that this PR is more reviewable as a unit.
I was a little confused because the CI was checking against black. I think this relates to a local problem of line length being max 79 characters now (I think maybe flake8 changed the default line length, or the max-line-length
option).
I'll revert the commit and see what's happening.
Oh, odd. I know we've retroactively applied black
to some-but-not-all legacy bluesky repos. I can't remember for sure whether we did it here, but the single quotes in the codebase suggest we haven't.
@danielballan
Found it!
https://github.com/bluesky/event-model/commit/01898f228dc365ceb766785120c707a9897eee36
I'm unsure why these things are changing now though... Maybe a new black release, I think I see some highlights in the recent black releases which match up (I used 23.9.1 locally) :thinking:
I'll run black on a different branch off of main and make a new PR.
Never mind, origin is already black compliant. This branch seems to have a very minor black change so I'll leave it here. Something must have been wrong locally in the last commit.
Ah, OK, that makes sense. I think we are good to merge then.
Closes #236
Putting on a new branch for cleanliness