Skip to content
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

One-off isort run #3196

Merged
merged 8 commits into from
Aug 23, 2019
Merged

One-off isort run #3196

merged 8 commits into from
Aug 23, 2019

Conversation

crusaderky
Copy link
Contributor

A one-off, manually vetted and tweaked isort run

@crusaderky
Copy link
Contributor Author

Ready for review and merge

@max-sixty
Copy link
Collaborator

I was thinking about doing this (and had done it a couple of times in the past). My only concern with doing it now is whether it's likely to exacerbate any merge conflicts from the black changes. I've found that merge conflicts scale super-linearly with changes, at least in frustration if not lines - if so potentially we could wait for the outstanding PRs to update and then rerun?

@crusaderky
Copy link
Contributor Author

Fine for me - is a week enough to allow everybody to adapt?

@crusaderky
Copy link
Contributor Author

Updated, re-run everything, and removed the blanket F401 (unused import) suppression.
Ready for final review and merge.

@max-sixty
Copy link
Collaborator

Great, +1 from me

@crusaderky crusaderky merged commit 79dc7dc into pydata:master Aug 23, 2019
@crusaderky crusaderky deleted the isort branch September 9, 2019 08:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants