ParamSpec allowed to be used before import
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 15.6k
- Forks
- 1.8k
- Avg merge
- 12h 13m
- Merged PRs (30d)
- 52
Description
Note: if you are reporting a wrong signature of a function or a class in the standard library, then the typeshed tracker is better suited for this report: https://github.com/python/typeshed/issues.
If you have a question about typing or a behavior that you’re seeing in Pyright (as opposed to a bug report or enhancement request), consider posting to the [Pyright discussion forum](https://github.com/microsoft/pyright/discussions).
**Describe the bug**
In the event that the ParamSpec or TypeVar constructs are used prior to being imported from the typing module, they don't report an error if they are imported after their first use.
**Code or Screenshots**
```python
P = ParamSpec("P") # Should error, doesn't
R = TypeVar("R")
from typing import TypeVar, ParamSpec
```
**Pyright-playground link**
https://pyright-play.net/?code=AoAgvCwIYE5QtgZQA4FMDGAKARMbBKAWACgAlcEAFQE80A1WHUgkkgMxgHt4QAXWgJYA7AOYgB8ZJxi8qtVAxgAaSLAQoMJIA
**version of pyright**
pyright 1.1.403
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Pyright playground link and reproduce the example using pyright 1.1.403, checking the diagnostics before the later typing import. The issue is done when ParamSpec and TypeVar uses before their imports report errors consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100