-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
ref(py3): pre-commit upgrade + sweeping rerun + __future__ removals #23197
Conversation
(cherry picked from commit 93c6b8c)
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.
unsubscribe
Do we need to do this for getsentry as well? |
I'm probably going to wait for #23195. @wedamija would also like your review on https://github.com/getsentry/getsentry/pull/4957. |
Oh, might as well just remove all the |
|
Ah backend lint cancelled at 3 min cap... @billyvg FYI this did not result in a "failure", I had to notice this. Bumping to 10 for now. |
Yeah cancelled jobs have a subtle gray icon but will count as a failure if the check is required (which can't happen on gs) |
lol
but other than this we lookin' good, gonna wait until monday, remerge, and do all of this for https://github.com/getsentry/getsentry/pull/4957 |
(cherry picked from commit eff5835)
Uhh, lol, guess I went at it too hard today.
|
For anyone rebasing/merging against this when it lands, you'll need to
make setup-git
and run pre-commit on the files you changed in your branch. Something likepre-commit run --files $(git whatchanged --name-only --pretty="" master... | sort | uniq)
.This upgrades pre-commit and its hooks, moves it into a
requirements-pre-commit.txt
for git hook notifications on updates, and reruns pre-commit on everything. Most notably, black's target-version py36 removesu
prefixes. flake8 is now run onbin/
and I manually made those fixes. Also removes all__future__
s (in our case we can remove everything).