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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Python] Add syntax highlighting for type comments #1925
[Python] Add syntax highlighting for type comments #1925
Changes from all commits
137308c
ed61bb4
56ff18e
482f0ec
14bf602
2a57368
e3b57a9
97ae638
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should probably be
meta_scope
so it applies to the(
and)
, right?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just for clarification
(I don't know how fine-grained these tests are here.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The impression I had gotten from the previous implementation was that line comments added into a type comment effectively ended the processing of mypy. Is that true?
From your comment above, it almost sounds like mypy will process nested comments that start with
type:
and the only logical combinations aretype: ignore
and a normaltype:
comment, right?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe mypy stops after the first
type: ignore
comment. 🤷 After that everything is "egal". The only thing you see in practice is# type: str # type: ignore
to brutally force a type. And typical# type: ignore[foo-rule] # mypy bug https:\\issue-nr
because you really get hit by a mypy bug every other day.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The parens in
(str, int)
are not allowed. It's actuallyTuple[str, int]
. They take explicit > implicit seriously.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am uncertain here. I've created a little test file with
Hovering
a
orb
with LSP and LSP-pylsp installed, doesn't show anything, while an example using current syntax with or without parentheses works fine.It also makes sense as I found some comments about such type hints to date back to python 2.7 which doesn't know about
typing
module.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The related spec can be found at https://mypy.readthedocs.io/en/stable/type_inference_and_annotations.html#declaring-multiple-variable-types-at-a-time