docs: explain conflict between C0209 and W1203#10680
Open
prerna0412 wants to merge 2 commits intopylint-dev:mainfrom
Open
docs: explain conflict between C0209 and W1203#10680prerna0412 wants to merge 2 commits intopylint-dev:mainfrom
prerna0412 wants to merge 2 commits intopylint-dev:mainfrom
Conversation
Pierre-Sassoulas
requested changes
Oct 19, 2025
Member
Pierre-Sassoulas
left a comment
There was a problem hiding this comment.
Thank you for working on this. I think it would make more sense to add this in a details.rst in the page specific to C0209 / W1203
Contributor
|
This PR needs take over because because it has been open 8 weeks with no activity. |
This file contains hidden or 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
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.
Type of Changes
Description
This adds documentation to clarify the conflict between the
C0209(consider-using-f-string) andW1203(logging-fstring-interpolation) messages.It explains why the conflict occurs and provides options to resolve it using message control in the pylintrc file.
Refs #XXXX
Closes #XXXX