Unparameterized `np.ndarray` typings produce "Type of ... is partially unknown" Pyright type errors.
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- numpy, python
- Área
- developer-experience, tooling
Línea de trabajo
Start by reproducing the issue with example.py, the strict Pyright configuration, and the LinearRegression.fit entry point. Trace the private MatrixLike alias in the sklearn.linear_model stubs, identify the unparameterized ndarray annotations involved, and run Pyright again to confirm the partially-unknown errors are resolved.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem
The type np.ndarray is stubbed in this library as:
class ndarray(_ArrayOrScalarCommon, Generic[_ShapeType, _DType_co]):
...
Throughout these stubs, the type np.ndarray is used without provided type parameters, seemingly with the expectation that this is treated as np.ndarray[Any, Any] (or more properly np.ndarray[object. object]). However, Pyright in strict mode alternately interprets this as np.ndarray[Unknown, Unknown].
As a result, every method that involves np.ndarray or a type alias which includes it produces a partially-unknown-type error:
Example Reproduction
For example, if we take the following simple file example.py...
import numpy as np
from typings.sklearn.linear_model import LinearRegression
def example():
x = np.array([1, 2, 3, 4, 5])
y = np.array([2, 4, 6, 8, 10])
linreg = LinearRegression()
linreg.fit(x, y)
❯ pyright src/path/to/example.py
src/path/to/example.py
src/path/to/example/example.py:11:5 - error: Type of "fit" is partially unknown
Type of "fit" is "(X: ndarray[Unknown, Unknown] | DataFrame | spmatrix | Buffer | _SupportsArray[dtype[Any]] | _NestedSequence[_SupportsArray[dtype[Any]]] | bool | int | float | complex | str | bytes | _NestedSequence[bool | int | float | complex | str | bytes], y: ndarray[Unknown, Unknown] | DataFrame | spmatrix | Buffer | _SupportsArray[dtype[Any]] | _NestedSequence[_SupportsArray[dtype[Any]]] | bool | int | float | complex | str | bytes | _NestedSequence[bool | int | float | complex | str | bytes], sample_weight: Buffer | _SupportsArray[dtype[Any]] | _NestedSequence[_SupportsArray[dtype[Any]]] | bool | int | float | complex | str | bytes | _NestedSequence[bool | int | float | complex | str | bytes] | None = None) -> LinearRegression"
In this case, the error occurs because the type of fit is:
def fit(
self: LinearRegression_Self,
X: MatrixLike | ArrayLike,
y: MatrixLike | ArrayLike,
sample_weight: None | ArrayLike = None,
) -> LinearRegression_Self:
...
And in turn MatrixLike is a (private) typealias that resolves to:
MatrixLike = np.ndarray | pd.DataFrame | spmatrix
Resolution
At least for this example, changing that type alias as follows resolves the type error.
MatrixLike = np.ndarray | pd.DataFrame | spmatrix
System Details:
OS: MacOS Sonoma 14.1.2
Python: CPython 3.12.1
Pyright: 1.1.358
Pyright configuration:
[tool.pyright]
include = ["./src", "./tests"]
stubPath = "./typings"
typeCheckingMode = "strict"
reportMissingImports = true
reportMissingTypeStubs = true
pythonVersion = "3.12"
- Lenguaje dominante
- Python
- Estrellas
- 304
- Forks
- 104
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoft/python-type-stubs
-
Maintenance Status Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
microsoft/python-type-stubs#395 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 58/100
microsoft/python-type-stubs#392 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 45/100
microsoft/python-type-stubs#345 ·
-
Inconsistent naming of stubs Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
microsoft/python-type-stubs#315 · 1 comentario ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
microsoft/python-type-stubs#211 · 8 comentarios · 29 reacciones ·
Todos los issues de microsoft/python-type-stubs
Issues similares
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
use-agent-os/agent-os#3314 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
BasedHardware/omi#15662 · 1 comentario ·
-
documentation help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
AiursoftWeb/AnduinOS-2#19 ·