Disable consider-using-f-string in pylint #473
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Aditya Sirish <aditya@saky.in>
adityasaky
force-pushed
the
ignore-f-string-recommendation
branch
from
ec43268
to
2988050
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please fill in the fields below to submit a pull request. The more information
that is provided, the better.
Fixes issue #: N/A.
Description of the changes being introduced by the pull request:
Disables
consider-using-f-stringin pylint. Our style guideline recommends using both f-strings and the currently used.formatmechanisms: https://github.com/secure-systems-lab/code-style-guidelines/blob/master/python.md#string-formatting, so IMO we shouldn't go and change the 94 (!) instances that the linter currently warns us about (https://github.com/in-toto/in-toto/pull/472/checks?check_run_id=3796490973).Please verify and check that the pull request fulfills the following
requirements: