Covariance error inferred for lambda has invalid line number associated with it
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 20.6k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
Versions
mypy 0.770
python 3.8.2
Description
This is probably related to the https://github.com/python/mypy/issues/4270
Problem is triggered when using recipe everything_except from hypothesis documentation:
https://hypothesis.readthedocs.io/en/latest/data.html#hypothesis.strategies.from_type
I have a file with following content (this is the whole file):
from typing import TypeVar
from hypothesis import strategies as st
_Ex = TypeVar("_Ex", covariant=True)
def everything_except(*types: type) -> st.SearchStrategy[_Ex]:
strategy = st.from_type(type).flatmap(st.from_type)
return strategy.filter(lambda x: not isinstance(x, types)) # type: ignore
Running mypy on first clean run (without .mypy_cache) has the following output:
example.py:1276: error: Cannot use a covariant type variable as a parameter
Found 1 error in 1 file (checked 1 source file)
For some reason, mypy sees error on line 1276 which does not exist. On the other hand, running mypy for the second time gives:
Success: no issues found in 1 source file
What's more, when you have pretty set to True, first run gives:
Traceback (most recent call last):
File "/home/krprzyby/.local/bin/mypy", line 8, in <module>
sys.exit(console_entry())
File "/home/krprzyby/.local/lib/python3.8/site-packages/mypy/__main__.py", line 8, in console_entry
main(None, sys.stdout, sys.stderr)
File "mypy/main.py", line 89, in main
File "mypy/build.py", line 180, in build
File "mypy/build.py", line 249, in _build
File "mypy/build.py", line 2649, in dispatch
File "mypy/build.py", line 2956, in process_graph
File "mypy/build.py", line 3073, in process_stale_scc
File "mypy/errors.py", line 476, in file_messages
File "mypy/errors.py", line 449, in format_messages
IndexError: list index out of range
Running mypy for the second time works correctly with pretty set to True because the line number is correct and # type: ignore works.
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
Reproduce the supplied example with an empty .mypy_cache and pretty output enabled. Start by reading mypy/errors.py and the related build.py paths shown in the traceback; done means the first run reports a valid source line and does not raise IndexError, while the type-ignore behavior remains consistent on subsequent runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100