Improve adherence to Python array API Standards

Abierto
  • ¿Algo no está bien?
#740 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Refactorización
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
numpy, python
Área
backend

Línea de trabajo

Start by reading PyLops’ backend module and the Python Array API Standards documentation, then compare the module’s current responsibilities with array-api-compat. The issue does not identify specific files or tests; first determine a concrete scope for adopting the standard. Done should mean an agreed, tested path toward better standard adherence, but the issue does not define that path.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement

Since v1.12.0, PyLops started to support alternative backends to NumPy, with the main goal of being able to perform computations (i.e., apply operators and solvers) on GPUs.

Initially, inter-operating different array/tensor libraries required "a lot" of manual work due to inconsistent APIs and lack of a unifying layer. As such we created the backend module to encapsulate as much of the boilerplate code and limit changes in the actual operator/solver implementations. This allow allowed us to have protected imports of optional libraries and fallback to NumPy when such libraries where not installed in the system.

Over time, the Python ecosystem has caught up with initiatives such as the Python Array API Standards that creates a unified standard that all array/tensor libraries have to adhere to. If a library adheres to the standard, it becomes easier to write a tensor-library agnostic code.

More recently application libraries that serve purposes similar to that of PyLops have started to adopt this standard, with scikit-learn being an example https://labs.quansight.org/blog/array-api-scikit-learn-2026. Also utility libraries have started to appear (e.g., array-api-compat which serve very similar purpose to what we do in the backend module.

It is maybe about time to start looking into this and unifying ourselves to the standard that started to appear and is now quite widely recognized and adopted.

Lenguaje dominante
Python
Estrellas
539
Forks
126
Merge medio
2 d 18 h
PR fusionados (30 d)
21

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de PyLops/pylops

Todos los issues de PyLops/pylops

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.