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

Keep the server's raw bytes, and allow sending given bytes unchanged

Abierto
  • ¿Algo no está bien?
#763 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
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
backend

Línea de trabajo

Start with _set_data() around line 1760 in calendarobjectresource.py and trace the GET, calendar-query, calendar-multiget, and save paths that call it or normalize data with vcal.fix(). The issue leaves the API shape open, so first read the linked calendaring design and compare these paths. Done means preserving the received bytes and offering an opt-in to send supplied bytes unchanged while retaining conditional request handling.

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

Descripción

enhancement

Disclaimer: AI-generated text below the line, generated by Claude Opus 5.5 (Claude Code), from the prompt:

Open the issue in the caldav library [comment made in a code-review document, on a finding that caldav's wire_data is not the bytes the server sent]

Low priority. Needed by the calendaring library's proposed Item.wire (https://github.com/pycalendar/calendaring, docs/design/API_DESIGN.md, "The stored form"), and by sync tools such as https://github.com/pycalendar/calendaring-sync, which compare and push the bytes a server stores.

Today a CalendarObjectResource cannot give back what the server sent:

  • _set_data() runs the incoming data through vcal.fix() before storing it in _data (calendarobjectresource.py, around line 1760), so the raw response body is gone right after parsing the response.
  • wire_data re-encodes _data (or serialises icalendar_instance / vobject_instance after an edit), so it is caldav's normalised copy, not the server's bytes, and not a snapshot of what was read.
  • When saving, the same path normalises bytes the caller passes in, so "store exactly these bytes" is not possible either.

Suggested shape (open for discussion):

  • Keep the unmodified response body of the last GET / calendar-query / calendar-multiget in a read-only attribute (e.g. raw_data), cleared by any write or local edit, next to the etag it belongs to.
  • An opt-in to send given bytes without vcal.fix() (e.g. save(raw=True), or setting raw_data before save()), still with If-Match / If-None-Match.

vcal.fix() stays the default; this is only about not throwing the original away.

Lenguaje dominante
Python
Estrellas
412
Forks
113
Merge medio
1 d 2 h
PR fusionados (30 d)
41

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.