Closed
Conversation
Member
|
Ah sorry, I should have explained for typos. In general, we don't fix typos that are not user-facing (that is, we only fix typos in docstrings, docs, error messages, etc, but usually, we don't fix typos in comments; that's to avoid having to backport them and to avoid code churn). If we were to rewrite the fnmatch() tests, then we would fix the typo because it's code that we would touch. Sorry, but this one won't be merged (we don't have an exact policy for typos... it's at the discretion of core devs, and the policy I take is shared by other core devs) |
Contributor
Author
|
@picnixz that's fair, I understand, no worries 👍 |
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
2 participants
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.
CC @picnixz