Repository navigation
TYP: np.maximum(np.array(1), np.array(1)) is Any in 2.2.2 while it wasn't in 2.2.1 #28193
Closed as duplicate
Description
Describe the issue:
numpy 2.2.2 reveals a different type for np.maximum(np.array(1), np.array(1)) than 2.2.1. This looks like a result of #28176. In contrast to #28192, which I think may be intended, I think this is unintended behavior.
This happens only with mypy, not pyright.
Reproduce the code example:
from typing import reveal_type
import numpy as np
reveal_type(np.maximum(np.array(1), np.array(1)))Error message:
2.2.2: Revealed type is "Any"
2.2.1: Revealed type is "numpy.ndarray[builtins.tuple[builtins.int, ...], numpy.dtype[Any]]"Python and NumPy Versions:
Numpy 2.2.2 vs 2.2.1
Type-checker version and settings:
mypy 1.14.1 (compiled: yes)
Additional typing packages.
No response
Activity
jorenham commentedon Jan 20, 2025
I think this is actually the same underlying problem as #28192, because
is reported as
Note that both
np.maximumand thenp.modfrom #28192 are instances of the same (type-check-only)_UFunc_Nin2_Nouttype.The 0-d arrays are not scalars, so the first
_UFunc_Nin2_Nout.__call__overload also isn't relevant. And just like in #28192, it's only mypy that infersAny, and pyright reports the following:np.mod(npt.NDArray, Any)isAnyin 2.2.2 while it wasn't in 2.2.1 #28192bersbersbers commentedon Jan 21, 2025
I opened python/mypy#18496.