Improve adherence to Python array API Standards

Aperta
  • Qualcosa non va?
#740 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Refactoring
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
numpy, python
Ambito
backend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Python
Stelle
539
Fork
126
Merge medio
2g 17h
PR unite (30g)
21

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di PyLops/pylops

Tutte le issue di PyLops/pylops

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.