Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Please consider archiving project or marking as deprecated

Aperta
#363 1 commento 8 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Documentazione
Chiarezza
Da chiarire
Stato di attività
Tranquilla
Stack tecnologico
python
Ambito
documentation, release

Direzione di ricerca

Esamina l’attività attuale del repository e i dettagli sull’adozione in issue #363, inclusi i riferimenti collegati a PyCapsule Interface e Narwhals. Determina se i maintainer hanno deciso di archiviare o deprecare il progetto; il lavoro è completo quando tale decisione e qualsiasi dichiarazione sulle lezioni apprese sono riportate nello stato e nella documentazione del repository.

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

Descrizione

Hi all 👋

I hope you're all well! I'd like to discuss what should happen to this repository and project going forwards

I think the Consortium had some good ideas, and I appreciate the efforts to improve tool composability. I have a lot of respect for everybody involved. We just need to recognise that activity has completely stalled, and the project seems to have been abandoned

This repository has been the home to two projects:

  • Dataframe interchange protocol. This hasn't been updated in 1.5+ years, and design issues haven't received responses nor fixes. I find this a bit disappointing, as a lot of code was submitted to pandas and maintenance then fell entirely on pandas' shoulders. Anyway, that ship has sailed, let's focus on deciding what happens next 🤝
  • Dataframe API standard. This never took off - it's a pity, because as it turned out there was quite a bit of demand for this, we just couldn't agree on fundamental design issues.

Regarding adoption of the former:

  • cuDF have removed support for it completely
  • I've moved pandas and Polars from_dataframe over to try using the PyCapsule Interface first. I hope nobody holds this against me, I don't think there was any other option
  • Consumers have generally moved away from it (either towards the PyCapsule Interface or towards Narwhals, or both in the case of Vegafusion). Scikit-learn use it for .column_names and for checking if a dtype is categorical, but that's about it, and those checks are easily replaceable

At this point - what next? To reduce fragmentation and avoid disappointing people, I'd like to suggest that this repository be archived and/or be marked as deprecated, possibly along with some statement about lessons learned?

I hope this message comes across well, and that you're all doing well ☺

Thank you for your consideration 🙏

Lingua principale
Python
Stelle
106
Fork
22
Nessuna PR unita negli ultimi 30g

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

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 data-apis/dataframe-api

Tutte le issue di data-apis/dataframe-api

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.