-
-
Notifications
You must be signed in to change notification settings - Fork 69
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
[1.0] Remove deprecations #460
Conversation
Closes #430
Seems like Pylint has updated again, ugh. |
this one: Formatting a regular string which could be a f-string (consider-using-f-string) |
It's good advice in most cases, except for logging (f-strings are greedy evaluated, as opposed to %-formatting). I will check if these warnings include logging statements - if so, we should probably disable it |
Looking through, they don't include logging statements, so I'd consider them all legit. I can open a separate PR which fixes, it's a lot of minor one-line rewrites |
so disable for now, address in separate PR? sounds good to me. |
Yeah, this is actually a huge pain. f-strings are great (easier to read imo, and also faster by a not-insignificant margin) but they do not play nicely with a short line length limit and long variable names. I'm just going to disable it for now, maybe we fix it one day maybe we don't. Tools like flynt can help with the conversion, but they won't catch all cases and won't do the manual line-splitting we need to satisfy flake8 at 80 characters |
Codecov Report
@@ Coverage Diff @@
## develop #460 +/- ##
===========================================
- Coverage 78.09% 77.71% -0.39%
===========================================
Files 30 20 -10
Lines 9255 5976 -3279
===========================================
- Hits 7228 4644 -2584
+ Misses 2027 1332 -695
Continue to review full report at Codecov.
|
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.
LGTM!
Merging in anticipation of a 1.0 (possibly a RC first) |
Closes #430. This should probably be the last thing we merge before cutting a release, hence the draft status.
Submission Checklist
Summary
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company):
Simons Foundation
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses: