Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Remove the old incompatibility flags completely

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

Los mantenedores suelen responder en 1 día

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
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
python
Área
backend-api-design

Línea de trabajo

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.

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

Descripción

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.

Lenguaje dominante
Python
Estrellas
412
Forks
113
Merge medio
10 h 20 min
PR fusionados (30 d)
57

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

Todos los issues de python-caldav/caldav

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.