-
-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
STY: Pylint f-string Errors C0209
#26278
Comments
We don't use pylint for our linting, nor have we adopted the policy of only using f-strings in all places where it is possible. Changing those usages to f-strings may or may not be desirable (weighed against the churn), but it's definitely not a bug. |
C0209
C0209
Got it, that makes sense. Yes, I realize that I should have marked this as an |
It's also not an enhancement, since that means an improvement visible to users. I marked it as maintenance. |
Describe the issue:
There are a number of areas throughout the
numpy
module that have Pylint linting issues, specifically in regards to using f-strings as opposed to the.format()
method. I noticed that PylintC0209
was particularly prevalent throughout the numpy repository, so I updated these linting errors.See Pylint
C0209
for more details.Reproduce the code example:
Error message:
Python and NumPy Versions:
Python version >= 3.6
Runtime Environment:
No response
Context for the issue:
No response
The text was updated successfully, but these errors were encountered: