Fix #2097: Recognize type comments with spaces after # #4652
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.
Fixes #2097
Description
Currently, Black fails to recognize
# type:
and# type: ignore
comments if there's extra whitespace after the#
(e.g.,# type:
), as described in issue #2097. This can lead to these comments being treated as regular comments, potentially causing incorrect formatting or instability.This PR updates the comment recognition logic (
is_type_comment
,is_type_ignore_comment
, and helper functions likeis_type_comment_string
/is_type_ignore_comment_string
) to correctly handle this leading whitespace after the#
. It allows comments like# type: value
and# type: ignore
to be correctly identified.As discussed in the issue thread, this change focuses only on fixing the recognition part of the bug and does not implement comment standardization (i.e., it doesn't reformat
# type:
to# type:
).Additionally, this PR includes a small fix for unrelated
mypy
errors ([import-untyped, unreachable]
) encountered inaction/main.py
which were required to pass local pre-commit checks.