Change identifier replacer to allow for all valid Python identifiers #202
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.
Overview
Change check for valid identifiers from
to using the stdlib Python functions
str.isidentifier
andkeyword.iskeyword
Details
The previous identifier pattern has two problems.
a) It blocks a lot of names as a lot of UTF-8 characters, e.g.
α
, are valid identifiersb) It doesn't block invalid keywords as Python names, e.g.
def
The stdlib
str.isidentifier
andkeyword.iskeyword
functions allow to correctly check for both cases and as a bonus are maintained by the Python folks, so new keyword additions etc. aren't a problemI replaced the check in the
IdentifierReplacer
class and added an additional check for thedef
keyword in the test cases.As a side note: is it necessary to check for the key to be a valid Python identifier? Since the key comes from parsing an existing Python function it cannot be invalid in the first place