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

Remove the old incompatibility flags completely

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

I maintainer di solito rispondono entro 1 giorno

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
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
python
Ambito
backend-api-design

Direzione di ricerca

Start by reading #402 and the incompatibility_description list in compatibililty_hints.py, then inspect FeatureSet.FEATURES, the caldav-server-tester checks, and the tests that use each flag. Work through flags individually, updating feature checks and considering API workarounds as described. Done means the old list is removed, affected tests use feature checks, and the changes are validated by running tests against incompatible servers.

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

Descrizione

In compatibililty_hints.py, there is a incompatibility_description list that should be removed.

For each flag in the list:

  • A better name for it needs to be found, suitable for including in the features structure
  • The features list (FeatureSet.FEATURES) should be updated to include it
  • The caldav-server-tester project should be fixed to check for it
  • Consider if it's possible to create work-arounds in the caldav code making consistent results from the API, regardless of server support. If it's easy, then it should be fixed, if it's not so easy, an issue could be recorded in the issue tracker, if it's very complicated or causes too much overhead, then "nevermind"
  • The test code should be amended to use the feature (self.is_supported(...) or self.skip_unless_support(...)) rather than the incompatibility flag.
  • All work needs to be validated by running tests (this means we need to be able to test the code towards incompatible servers to be able to move things).

This is a continuation of #402 - more information can be found there.

It involves quite some work, typically several hours of work for each flag, and there are A LOT of them (though I've killed quie a lot already). I found Claude to be quite helpful at this, though it's needed to review the changes proposed by claude.

Lingua principale
Python
Stelle
412
Fork
113
Merge medio
1g 7h
PR unite (30g)
34

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 python-caldav/caldav

Tutte le issue di python-caldav/caldav

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.