Repository navigation
BUG: typings: a - b returns NoReturn instead of ndarray #20265
Description
Describe the issue:
Running
pyright foo.py
on
import numpy as np
def myfun(x: np.ndarray, b: np.ndarray):
v = b - x
v.copy()gives
/tmp/dummy.py:6:7 - error: Cannot access member "copy" for type "NoReturn"
Member "copy" is unknown (reportGeneralTypeIssues)
The vector operations +, *, / work fine.
NumPy/Python version information:
1.21.3 3.9.7 (default, Sep 10 2021, 14:59:43)
[GCC 11.2.0]
Activity
BvB93 commentedon Nov 1, 2021
Duplicate of #20099 and (to some extent) #20072.
Interestingly, it appears that this bug is not limited to mypy (xref python/mypy#11347).
Annoying as it is, I'm wondering if it might be best to temporarily remove the dunder overloads...
nschloe commentedon Nov 1, 2021
It's funny that only
-is concerned, not+,*, or/.BvB93 commentedon Nov 1, 2021
The problem is that
selfannotations are ignored when aAny-parametrized object is passed to an overload method.So what happens is that
np.ndarray(or equivalentlynp.ndarray[Any, Any]) will just pick whatever happens to be the first overload, which turns out to be toNoReturnoverload used for boolean arrays:numpy/numpy/__init__.pyi
Lines 2013 to 2014 in fa397e9
BvB93 commentedon Nov 1, 2021
Closing this in favor of #20099