icalendar 7.2.2__tar.gz → 7.3.2__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (578) hide show
  1. icalendar-7.3.2/.claude/settings.json +16 -0
  2. {icalendar-7.2.2 → icalendar-7.3.2}/.gitignore +2 -0
  3. {icalendar-7.2.2 → icalendar-7.3.2}/Makefile +14 -0
  4. {icalendar-7.2.2 → icalendar-7.3.2}/PKG-INFO +6 -3
  5. {icalendar-7.2.2 → icalendar-7.3.2}/README.rst +3 -0
  6. icalendar-7.3.2/docs/_include/maintainers.inc +4 -0
  7. {icalendar-7.2.2 → icalendar-7.3.2}/docs/_static/version-switcher.json +1 -1
  8. {icalendar-7.2.2 → icalendar-7.3.2}/docs/contribute/credits.rst +5 -3
  9. {icalendar-7.2.2 → icalendar-7.3.2}/docs/contribute/development.rst +34 -0
  10. {icalendar-7.2.2 → icalendar-7.3.2}/docs/contribute/documentation/build-check.rst +2 -2
  11. {icalendar-7.2.2 → icalendar-7.3.2}/docs/contribute/documentation/style-guide.rst +47 -8
  12. {icalendar-7.2.2 → icalendar-7.3.2}/docs/contribute/index.rst +67 -10
  13. icalendar-7.3.2/docs/contribute/join-the-icalendar-team.rst +97 -0
  14. {icalendar-7.2.2 → icalendar-7.3.2}/docs/contribute/maintenance.rst +11 -4
  15. {icalendar-7.2.2 → icalendar-7.3.2}/docs/how-to/parse-errors.rst +1 -1
  16. {icalendar-7.2.2 → icalendar-7.3.2}/docs/styles/config/vocabularies/icalendar/accept.txt +2 -0
  17. icalendar-7.3.2/docs/styles/config/vocabularies/icalendar/reject.txt +1 -0
  18. icalendar-7.3.2/funding.json +113 -0
  19. {icalendar-7.2.2 → icalendar-7.3.2}/pyproject.toml +9 -0
  20. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/__init__.py +4 -0
  21. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/_version.py +2 -2
  22. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/alarms.py +11 -3
  23. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/attr.py +96 -18
  24. icalendar-7.3.2/src/icalendar/cal/alarm.py +716 -0
  25. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/cal/availability.py +3 -2
  26. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/cal/available.py +4 -2
  27. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/cal/calendar.py +115 -130
  28. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/cal/component.py +76 -63
  29. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/cal/component_factory.py +2 -2
  30. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/cal/event.py +14 -8
  31. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/cal/free_busy.py +39 -6
  32. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/cal/journal.py +30 -4
  33. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/cal/lazy.py +4 -4
  34. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/cal/todo.py +14 -8
  35. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/cli.py +5 -0
  36. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/enums.py +4 -3
  37. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/error.py +111 -3
  38. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/parser/content_line.py +40 -19
  39. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/parser/ical/component.py +8 -1
  40. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/parser/ical/lazy.py +1 -1
  41. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/parser/parameter.py +3 -2
  42. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/parser/string.py +28 -16
  43. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/adr.py +1 -1
  44. icalendar-7.3.2/src/icalendar/prop/binary.py +146 -0
  45. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/boolean.py +19 -15
  46. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/cal_address.py +4 -0
  47. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/categories.py +1 -1
  48. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/dt/date.py +1 -1
  49. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/dt/datetime.py +1 -1
  50. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/dt/duration.py +3 -1
  51. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/dt/list.py +1 -1
  52. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/dt/period.py +104 -56
  53. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/dt/time.py +10 -7
  54. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/dt/types.py +4 -2
  55. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/dt/utc_offset.py +1 -1
  56. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/factory.py +4 -7
  57. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/geo.py +1 -1
  58. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/image.py +2 -3
  59. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/inline.py +4 -0
  60. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/integer.py +2 -0
  61. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/n.py +1 -1
  62. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/org.py +2 -10
  63. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/recur/recur.py +6 -1
  64. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/recur/weekday.py +8 -1
  65. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/text.py +8 -1
  66. icalendar-7.3.2/src/icalendar/prop/unknown.py +149 -0
  67. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/uri.py +5 -1
  68. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/attr/test_alarm.py +20 -1
  69. icalendar-7.3.2/src/icalendar/tests/attr/test_alarm_factory_methods.py +251 -0
  70. icalendar-7.3.2/src/icalendar/tests/attr/test_issue_1594.py +135 -0
  71. icalendar-7.3.2/src/icalendar/tests/calendars/fuzz_testcase_vtimezone_lone_cr.ics +3 -0
  72. icalendar-7.3.2/src/icalendar/tests/calendars/issue_1549_binary_attachment.ics +8 -0
  73. icalendar-7.3.2/src/icalendar/tests/calendars/issue_1561_image_value.ics +18 -0
  74. icalendar-7.3.2/src/icalendar/tests/calendars/issue_1633_freebusy_with_dates.ics +7 -0
  75. icalendar-7.3.2/src/icalendar/tests/calendars/issue_1633_rdate_with_dates.ics +7 -0
  76. icalendar-7.3.2/src/icalendar/tests/calendars/issue_1633_rdate_with_dates_and_tzid.ics +7 -0
  77. icalendar-7.3.2/src/icalendar/tests/calendars/issue_313_globally_unique_tzid.ics +22 -0
  78. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/conftest.py +16 -2
  79. icalendar-7.3.2/src/icalendar/tests/events/issue_100_transformed_doctests_into_unittests.ics +3 -0
  80. icalendar-7.3.2/src/icalendar/tests/freebusy/example.ics +11 -0
  81. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/fuzzed/__init__.py +1 -0
  82. icalendar-7.3.2/src/icalendar/tests/journals/example.ics +7 -0
  83. icalendar-7.3.2/src/icalendar/tests/prop/test_crlf_in_values.py +64 -0
  84. icalendar-7.3.2/src/icalendar/tests/prop/test_vBinary.py +210 -0
  85. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/prop/test_vWeekday.py +18 -0
  86. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/prop/test_windows_to_olson_mapping.py +10 -1
  87. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_7265_jcal/test_invalid_jcal.py +96 -13
  88. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_7265_jcal/test_section_3_6_values.py +1 -1
  89. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_7265_jcal/test_section_5_3_examples.py +1 -1
  90. icalendar-7.3.2/src/icalendar/tests/rfc_7265_jcal/test_uri_parameters_round_trip.py +74 -0
  91. icalendar-7.3.2/src/icalendar/tests/test_docstrings.py +235 -0
  92. icalendar-7.3.2/src/icalendar/tests/test_enums.py +77 -0
  93. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_examples.py +40 -3
  94. icalendar-7.3.2/src/icalendar/tests/test_generate_windows_to_olson_mapping.py +101 -0
  95. icalendar-7.3.2/src/icalendar/tests/test_ical_parsing_error.py +96 -0
  96. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_image.py +45 -5
  97. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_1050_lazy_parsing.py +1 -1
  98. icalendar-7.3.2/src/icalendar/tests/test_issue_1445.py +224 -0
  99. icalendar-7.3.2/src/icalendar/tests/test_issue_1569_singletons_multiple_consistency.py +32 -0
  100. icalendar-7.3.2/src/icalendar/tests/test_issue_1633.py +197 -0
  101. icalendar-7.3.2/src/icalendar/tests/test_issue_313_globally_unique_tzid.py +78 -0
  102. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_716_alarm_time_computation.py +39 -1
  103. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_756_read_calendar_from_file.py +22 -5
  104. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_798_property_parameters.py +2 -1
  105. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_843_new_method_for_components.py +81 -0
  106. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_parsing.py +74 -1
  107. icalendar-7.3.2/src/icalendar/tests/test_prop_org_coverage.py +135 -0
  108. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_pytz_zoneinfo_integration.py +25 -1
  109. icalendar-7.3.2/src/icalendar/tests/test_request_status.py +67 -0
  110. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_time.py +1 -1
  111. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_unit_caselessdict.py +14 -0
  112. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_unit_parser_tools.py +3 -0
  113. icalendar-7.3.2/src/icalendar/tests/test_windows_to_olson_version.py +12 -0
  114. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/timezone/equivalent_timezone_ids.py +2 -0
  115. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/timezone/pytz.py +5 -1
  116. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/timezone/tzp.py +58 -11
  117. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/timezone/windows_to_olson.py +57 -14
  118. icalendar-7.2.2/docs/styles/config/vocabularies/icalendar/reject.txt +0 -0
  119. icalendar-7.2.2/src/icalendar/cal/alarm.py +0 -364
  120. icalendar-7.2.2/src/icalendar/prop/binary.py +0 -85
  121. icalendar-7.2.2/src/icalendar/prop/unknown.py +0 -26
  122. icalendar-7.2.2/src/icalendar/tests/events/issue_100_transformed_doctests_into_unittests.ics +0 -3
  123. icalendar-7.2.2/src/icalendar/tests/prop/test_vBinary.py +0 -76
  124. icalendar-7.2.2/src/icalendar/tests/test_enums.py +0 -35
  125. {icalendar-7.2.2 → icalendar-7.3.2}/LICENSE.rst +0 -0
  126. {icalendar-7.2.2 → icalendar-7.3.2}/docs/_include/configure-git-card-dev.inc +0 -0
  127. {icalendar-7.2.2 → icalendar-7.3.2}/docs/_include/configure-git-card-doc.inc +0 -0
  128. {icalendar-7.2.2 → icalendar-7.3.2}/docs/_include/configure-git-steps.inc +0 -0
  129. {icalendar-7.2.2 → icalendar-7.3.2}/docs/_include/configure-git.inc +0 -0
  130. {icalendar-7.2.2 → icalendar-7.3.2}/docs/_include/prerequisites.inc +0 -0
  131. {icalendar-7.2.2 → icalendar-7.3.2}/docs/_static/contributing/development-disable-pre-commit.png +0 -0
  132. {icalendar-7.2.2 → icalendar-7.3.2}/docs/_static/contributing/development-icalendar-git-workflow.svg +0 -0
  133. {icalendar-7.2.2 → icalendar-7.3.2}/docs/_static/edit-pencil-icon.png +0 -0
  134. {icalendar-7.2.2 → icalendar-7.3.2}/docs/_static/js/custom-icons.js +0 -0
  135. {icalendar-7.2.2 → icalendar-7.3.2}/docs/_templates/404.html +0 -0
  136. {icalendar-7.2.2 → icalendar-7.3.2}/docs/_templates/donate.html +0 -0
  137. {icalendar-7.2.2 → icalendar-7.3.2}/docs/_templates/nlnet.html +0 -0
  138. {icalendar-7.2.2 → icalendar-7.3.2}/docs/_templates/rtd-pr-previews.html +0 -0
  139. {icalendar-7.2.2 → icalendar-7.3.2}/docs/conf.py +0 -0
  140. {icalendar-7.2.2 → icalendar-7.3.2}/docs/contribute/code-of-conduct.rst +0 -0
  141. {icalendar-7.2.2 → icalendar-7.3.2}/docs/contribute/documentation/index.rst +0 -0
  142. {icalendar-7.2.2 → icalendar-7.3.2}/docs/contribute/documentation/small-edits.rst +0 -0
  143. {icalendar-7.2.2 → icalendar-7.3.2}/docs/explanation/api-design.rst +0 -0
  144. {icalendar-7.2.2 → icalendar-7.3.2}/docs/explanation/index.rst +0 -0
  145. {icalendar-7.2.2 → icalendar-7.3.2}/docs/how-to/attendees.rst +0 -0
  146. {icalendar-7.2.2 → icalendar-7.3.2}/docs/how-to/cli.rst +0 -0
  147. {icalendar-7.2.2 → icalendar-7.3.2}/docs/how-to/configure.rst +0 -0
  148. {icalendar-7.2.2 → icalendar-7.3.2}/docs/how-to/custom-components.rst +0 -0
  149. {icalendar-7.2.2 → icalendar-7.3.2}/docs/how-to/fuzz-testing-log.txt +0 -0
  150. {icalendar-7.2.2 → icalendar-7.3.2}/docs/how-to/fuzz-testing.rst +0 -0
  151. {icalendar-7.2.2 → icalendar-7.3.2}/docs/how-to/index.rst +0 -0
  152. {icalendar-7.2.2 → icalendar-7.3.2}/docs/how-to/install.rst +0 -0
  153. {icalendar-7.2.2 → icalendar-7.3.2}/docs/how-to/jcal.rst +0 -0
  154. {icalendar-7.2.2 → icalendar-7.3.2}/docs/how-to/upgrade.rst +0 -0
  155. {icalendar-7.2.2 → icalendar-7.3.2}/docs/how-to/usage.rst +0 -0
  156. {icalendar-7.2.2 → icalendar-7.3.2}/docs/index.rst +0 -0
  157. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.alarms.rst +0 -0
  158. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.attr.rst +0 -0
  159. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.cal.alarm.rst +0 -0
  160. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.cal.availability.rst +0 -0
  161. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.cal.available.rst +0 -0
  162. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.cal.calendar.rst +0 -0
  163. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.cal.component.rst +0 -0
  164. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.cal.component_factory.rst +0 -0
  165. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.cal.event.rst +0 -0
  166. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.cal.examples.rst +0 -0
  167. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.cal.free_busy.rst +0 -0
  168. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.cal.journal.rst +0 -0
  169. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.cal.lazy.rst +0 -0
  170. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.cal.rst +0 -0
  171. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.cal.timezone.rst +0 -0
  172. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.cal.todo.rst +0 -0
  173. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.caselessdict.rst +0 -0
  174. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.cli.rst +0 -0
  175. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.compatibility.rst +0 -0
  176. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.config.rst +0 -0
  177. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.enums.rst +0 -0
  178. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.error.rst +0 -0
  179. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.param.rst +0 -0
  180. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.parser.content_line.rst +0 -0
  181. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.parser.ical.calendar.rst +0 -0
  182. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.parser.ical.component.rst +0 -0
  183. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.parser.ical.lazy.rst +0 -0
  184. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.parser.ical.rst +0 -0
  185. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.parser.parameter.rst +0 -0
  186. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.parser.property.rst +0 -0
  187. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.parser.rst +0 -0
  188. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.parser.string.rst +0 -0
  189. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.parser_tools.rst +0 -0
  190. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.adr.rst +0 -0
  191. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.binary.rst +0 -0
  192. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.boolean.rst +0 -0
  193. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.broken.rst +0 -0
  194. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.cal_address.rst +0 -0
  195. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.categories.rst +0 -0
  196. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.conference.rst +0 -0
  197. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.dt.base.rst +0 -0
  198. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.dt.date.rst +0 -0
  199. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.dt.datetime.rst +0 -0
  200. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.dt.duration.rst +0 -0
  201. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.dt.list.rst +0 -0
  202. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.dt.period.rst +0 -0
  203. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.dt.rst +0 -0
  204. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.dt.time.rst +0 -0
  205. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.dt.types.rst +0 -0
  206. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.dt.utc_offset.rst +0 -0
  207. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.factory.rst +0 -0
  208. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.float.rst +0 -0
  209. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.geo.rst +0 -0
  210. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.image.rst +0 -0
  211. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.inline.rst +0 -0
  212. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.integer.rst +0 -0
  213. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.n.rst +0 -0
  214. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.org.rst +0 -0
  215. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.recur.frequency.rst +0 -0
  216. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.recur.month.rst +0 -0
  217. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.recur.recur.rst +0 -0
  218. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.recur.rst +0 -0
  219. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.recur.skip.rst +0 -0
  220. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.recur.weekday.rst +0 -0
  221. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.rst +0 -0
  222. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.text.rst +0 -0
  223. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.uid.rst +0 -0
  224. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.unknown.rst +0 -0
  225. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.uri.rst +0 -0
  226. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.prop.xml_reference.rst +0 -0
  227. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.rst +0 -0
  228. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.timezone.equivalent_timezone_ids.rst +0 -0
  229. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.timezone.provider.rst +0 -0
  230. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.timezone.pytz.rst +0 -0
  231. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.timezone.rst +0 -0
  232. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.timezone.tzid.rst +0 -0
  233. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.timezone.tzp.rst +0 -0
  234. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.timezone.windows_to_olson.rst +0 -0
  235. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.timezone.zoneinfo.rst +0 -0
  236. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.tools.rst +0 -0
  237. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/icalendar.version.rst +0 -0
  238. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/api/modules.rst +0 -0
  239. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/changelog.rst +0 -0
  240. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/glossary.rst +0 -0
  241. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/index.rst +0 -0
  242. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/rfc-support.rst +0 -0
  243. {icalendar-7.2.2 → icalendar-7.3.2}/docs/reference/versions-branches.rst +0 -0
  244. {icalendar-7.2.2 → icalendar-7.3.2}/docs/styles/config/vocabularies/Base/accept.txt +0 -0
  245. {icalendar-7.2.2 → icalendar-7.3.2}/docs/styles/config/vocabularies/Base/reject.txt +0 -0
  246. {icalendar-7.2.2 → icalendar-7.3.2}/docs/tutorials/create-event-with-attendees.rst +0 -0
  247. {icalendar-7.2.2 → icalendar-7.3.2}/docs/tutorials/example.ics +0 -0
  248. {icalendar-7.2.2 → icalendar-7.3.2}/docs/tutorials/index.rst +0 -0
  249. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/cal/__init__.py +0 -0
  250. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/cal/examples.py +0 -0
  251. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/cal/timezone.py +0 -0
  252. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/caselessdict.py +0 -0
  253. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/compatibility.py +0 -0
  254. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/config.py +0 -0
  255. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/param.py +0 -0
  256. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/parser/__init__.py +0 -0
  257. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/parser/ical/__init__.py +0 -0
  258. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/parser/ical/calendar.py +0 -0
  259. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/parser/property.py +0 -0
  260. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/parser_tools.py +0 -0
  261. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/__init__.py +0 -0
  262. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/broken.py +0 -0
  263. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/conference.py +0 -0
  264. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/dt/__init__.py +0 -0
  265. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/dt/base.py +0 -0
  266. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/float.py +0 -0
  267. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/recur/__init__.py +0 -0
  268. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/recur/frequency.py +0 -0
  269. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/recur/month.py +0 -0
  270. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/recur/skip.py +0 -0
  271. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/uid.py +0 -0
  272. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/prop/xml_reference.py +0 -0
  273. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/py.typed +0 -0
  274. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/__init__.py +0 -0
  275. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/alarms/example.ics +0 -0
  276. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/alarms/rfc_5545_absolute_alarm_example.ics +0 -0
  277. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/alarms/rfc_5545_end.ics +0 -0
  278. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/alarms/start_date.ics +0 -0
  279. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/attr/__init__.py +0 -0
  280. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/attr/test_component.py +0 -0
  281. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/attr/test_exdates.py +0 -0
  282. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/attr/test_rdate.py +0 -0
  283. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/attr/test_rrule.py +0 -0
  284. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/availabilities/rfc_7953_1.ics +0 -0
  285. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/availabilities/rfc_7953_2.ics +0 -0
  286. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/alarm_etar_future.ics +0 -0
  287. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/alarm_etar_notification.ics +0 -0
  288. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/alarm_etar_notification_clicked.ics +0 -0
  289. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/alarm_google_acknowledged.ics +0 -0
  290. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/alarm_google_future.ics +0 -0
  291. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/alarm_thunderbird_2_future.ics +0 -0
  292. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/alarm_thunderbird_2_notification_5_min_postponed.ics +0 -0
  293. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/alarm_thunderbird_2_notification_5_min_postponed_and_closed.ics +0 -0
  294. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/alarm_thunderbird_2_notification_5_min_postponed_and_popped_up.ics +0 -0
  295. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/alarm_thunderbird_2_notification_popped_up.ics +0 -0
  296. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/alarm_thunderbird_closed.ics +0 -0
  297. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/alarm_thunderbird_future.ics +0 -0
  298. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/alarm_thunderbird_snoozed_until_1457.ics +0 -0
  299. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/america_new_york.ics +0 -0
  300. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/america_new_york_forward_reference.ics +0 -0
  301. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/big_bad_calendar.ics +0 -0
  302. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/bom_calendar.ics +0 -0
  303. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/broken_dtstart.ics +0 -0
  304. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/broken_ical.ics +0 -0
  305. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/calendar_with_unicode.ics +0 -0
  306. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/created_calendar_with_unicode_fields.ics +0 -0
  307. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/empty.ics +0 -0
  308. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/empty_RDATE.ics +0 -0
  309. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/example.ics +0 -0
  310. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/fuzz_testcase_0_char_in_component_name.ics +0 -0
  311. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/fuzz_testcase_invalid_month.ics +0 -0
  312. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/invalid_duration.ics +0 -0
  313. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_104_broken_calendar.ics +0 -0
  314. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1050_all_components.ics +0 -0
  315. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1050_calendar_with_events_and_todos.ics +0 -0
  316. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1050_empty_calendar.ics +0 -0
  317. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1050_forward_timezone_reference.ics +0 -0
  318. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1050_multiple_calendars.ics +0 -0
  319. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1050_simple_calendar.ics +0 -0
  320. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1050_timezone_only_calendar.ics +0 -0
  321. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1050_uid_in_description.ics +0 -0
  322. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1081_empty_rdate.ics +0 -0
  323. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1081_event_with_rrule.ics +0 -0
  324. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1081_freebusy_comma_separated.ics +0 -0
  325. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1081_invalid_rrule_freq.ics +0 -0
  326. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1081_invalid_start_and_end.ics +0 -0
  327. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1081_invalid_start_valid_end.ics +0 -0
  328. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1081_list_of_properties.ics +0 -0
  329. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1081_tzid_param.ics +0 -0
  330. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1081_with_summary.ics +0 -0
  331. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1231_recurrence.ics +0 -0
  332. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1237_x_property.jcal +0 -0
  333. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1238.ics +0 -0
  334. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_127_categories_with_commas.ics +0 -0
  335. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1426.ics +0 -0
  336. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_1426_value_parameters.ics +0 -0
  337. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_156_RDATE_with_PERIOD_TZID_khal.ics +0 -0
  338. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_156_RDATE_with_PERIOD_TZID_khal_2.ics +0 -0
  339. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_165_missing_event.ics +0 -0
  340. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_168_expected_output.ics +0 -0
  341. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_168_input.ics +0 -0
  342. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_178_component_with_invalid_name_represented.ics +0 -0
  343. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_178_custom_component_contains_other.ics +0 -0
  344. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_178_custom_component_inside_other.ics +0 -0
  345. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_218_bad_tzid.ics +0 -0
  346. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_237_fail_to_parse_timezone_with_non_ascii_tzid.ics +0 -0
  347. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_27_multiple_periods_in_freebusy_multiple_freebusies.ics +0 -0
  348. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_27_multiple_periods_in_freebusy_one_freebusy.ics +0 -0
  349. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_321_assert_dst_offset_is_not_false.ics +0 -0
  350. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_322_expected_calendar.ics +0 -0
  351. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_348_exception_parsing_value.ics +0 -0
  352. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_350.ics +0 -0
  353. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_351_whitespace_in_property_and_params.ics +0 -0
  354. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_466_convert_tzid_with_slash.ics +0 -0
  355. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_466_respect_unique_timezone.ics +0 -0
  356. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_526_calendar_with_different_events.ics +0 -0
  357. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_526_calendar_with_event_subset.ics +0 -0
  358. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_526_calendar_with_events.ics +0 -0
  359. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_526_calendar_with_shuffeled_events.ics +0 -0
  360. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_722_missing_VTIMEZONE_custom.ics +0 -0
  361. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_722_missing_timezones.ics +0 -0
  362. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_722_timezone_transition_ambiguity.ics +0 -0
  363. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_798_freebusy.ics +0 -0
  364. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_798_related_to.ics +0 -0
  365. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_82_expected_output.ics +0 -0
  366. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/issue_836_do_not_quote_tzid.ics +0 -0
  367. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/multiple_calendar_components.ics +0 -0
  368. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/multiple_timezones.ics +0 -0
  369. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/pacific_fiji.ics +0 -0
  370. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/parsing_error.ics +0 -0
  371. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/parsing_error_in_UTC_offset.ics +0 -0
  372. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/period_with_timezone.ics +0 -0
  373. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/pr_480_summary_with_colon.ics +0 -0
  374. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/property_params.ics +0 -0
  375. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/rfc_5545_RDATE_example.ics +0 -0
  376. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/rfc_6868.ics +0 -0
  377. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/rfc_7256_multi_value_parameters.ics +0 -0
  378. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/rfc_7265_appendix_example_1_ical.ics +0 -0
  379. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/rfc_7265_appendix_example_1_jcal.jcal +0 -0
  380. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/rfc_7265_appendix_example_2_ical.ics +0 -0
  381. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/rfc_7265_appendix_example_2_jcal.jcal +0 -0
  382. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/rfc_7265_example_1.ics +0 -0
  383. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/rfc_7265_example_2.jcal +0 -0
  384. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/rfc_7265_example_3.jcal +0 -0
  385. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/rfc_7529.ics +0 -0
  386. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/rfc_7953_3.ics +0 -0
  387. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/rfc_7986_conferences.ics +0 -0
  388. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/rfc_7986_image.ics +0 -0
  389. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/rfc_7986_properties.ics +0 -0
  390. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/rfc_9253_examples.ics +0 -0
  391. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/rfc_9253_gap.ics +0 -0
  392. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/rfc_9253_related_to.ics +0 -0
  393. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/small_bad_calendar.ics +0 -0
  394. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/time.ics +0 -0
  395. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/timezone_rdate.ics +0 -0
  396. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/timezone_same_start.ics +0 -0
  397. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/timezone_same_start_and_offset.ics +0 -0
  398. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/timezoned.ics +0 -0
  399. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/calendars/x_location.ics +0 -0
  400. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/data.py +0 -0
  401. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/event_with_escaped_character1.ics +0 -0
  402. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/event_with_escaped_character2.ics +0 -0
  403. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/event_with_escaped_character3.ics +0 -0
  404. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/event_with_escaped_character4.ics +0 -0
  405. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/event_with_escaped_characters.ics +0 -0
  406. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/event_with_recurrence.ics +0 -0
  407. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/event_with_recurrence_exdates_on_different_lines.ics +0 -0
  408. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/event_with_rsvp.ics +0 -0
  409. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/event_with_unicode_fields.ics +0 -0
  410. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/event_with_unicode_organizer.ics +0 -0
  411. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/issue_101_icalendar_chokes_on_umlauts_in_organizer.ics +0 -0
  412. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/issue_104_mark_events_broken.ics +0 -0
  413. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/issue_112_missing_tzinfo_on_exdate.ics +0 -0
  414. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/issue_156_RDATE_with_PERIOD.ics +0 -0
  415. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/issue_156_RDATE_with_PERIOD_list.ics +0 -0
  416. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/issue_157_removes_trailing_semicolon.ics +0 -0
  417. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/issue_184_broken_representation_of_period.ics +0 -0
  418. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/issue_355_url_escaping.ics +0 -0
  419. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/issue_355_url_escaping_2.ics +0 -0
  420. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/issue_355_url_escaping_empty_param.ics +0 -0
  421. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/issue_464_invalid_rdate.ics +0 -0
  422. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/issue_53_description_parsed_properly.ics +0 -0
  423. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/issue_64_event_with_ascii_summary.ics +0 -0
  424. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/issue_64_event_with_non_ascii_summary.ics +0 -0
  425. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/issue_70_rrule_causes_attribute_error.ics +0 -0
  426. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/issue_82_expected_output.ics +0 -0
  427. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/rfc_7265_example_4.ics +0 -0
  428. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/rfc_7265_request_status.ics +0 -0
  429. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/rfc_9074_example_1.ics +0 -0
  430. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/rfc_9074_example_2.ics +0 -0
  431. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/rfc_9074_example_3.ics +0 -0
  432. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/rfc_9074_example_4.ics +0 -0
  433. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/events/rfc_9074_example_proximity.ics +0 -0
  434. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/fuzzed/generate_python_test_cases_from_downloaded_clusterfuzz_test_cases.sh +0 -0
  435. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/fuzzed/test_fuzzed_calendars.py +0 -0
  436. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/hypothesis/test_fuzzing.py +0 -0
  437. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/prop/__init__.py +0 -0
  438. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/prop/test_common_functionality.py +0 -0
  439. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/prop/test_conference.py +0 -0
  440. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/prop/test_constructors.py +0 -0
  441. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/prop/test_date_and_time.py +0 -0
  442. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/prop/test_duration_overflow.py +0 -0
  443. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/prop/test_identity_and_equality.py +0 -0
  444. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/prop/test_property_values.py +0 -0
  445. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/prop/test_trailing_newline.py +0 -0
  446. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/prop/test_unit.py +0 -0
  447. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/prop/test_vBoolean.py +0 -0
  448. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/prop/test_vCalAddress.py +0 -0
  449. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/prop/test_vDDDTypes.py +0 -0
  450. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/prop/test_vDatetime.py +0 -0
  451. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/prop/test_vFloat.py +0 -0
  452. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/prop/test_vFrequency.py +0 -0
  453. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/prop/test_vInt.py +0 -0
  454. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/prop/test_vPeriod.py +0 -0
  455. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_6350_vcard/__init__.py +0 -0
  456. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_6350_vcard/test_component_integration.py +0 -0
  457. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_6350_vcard/test_split_on_unescaped_semicolon.py +0 -0
  458. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_6350_vcard/test_vAdr.py +0 -0
  459. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_6350_vcard/test_vN.py +0 -0
  460. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_6350_vcard/test_vOrg.py +0 -0
  461. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_7265_jcal/__init__.py +0 -0
  462. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_7265_jcal/test_additional_considerations.py +0 -0
  463. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_7265_jcal/test_categories.py +0 -0
  464. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_7265_jcal/test_examples.py +0 -0
  465. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_7265_jcal/test_section_3_3_components.py +0 -0
  466. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_7265_jcal/test_section_3_4_properties.py +0 -0
  467. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_7265_jcal/test_section_3_5_parameters.py +0 -0
  468. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_7265_jcal/test_section_4_ical_parsing.py +0 -0
  469. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_9253_icalendar_relationships/__init__.py +0 -0
  470. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_9253_icalendar_relationships/test_concept.py +0 -0
  471. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_9253_icalendar_relationships/test_gap.py +0 -0
  472. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_9253_icalendar_relationships/test_link.py +0 -0
  473. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_9253_icalendar_relationships/test_new_property_types.py +0 -0
  474. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_9253_icalendar_relationships/test_refid.py +0 -0
  475. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/rfc_9253_icalendar_relationships/test_related_to.py +0 -0
  476. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_bom_calendar.py +0 -0
  477. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_categories_value_with_colon.py +0 -0
  478. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_cli_tool.py +0 -0
  479. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_compatibility.py +0 -0
  480. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_component_register.py +0 -0
  481. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_components_break_on_bad_ics.py +0 -0
  482. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_consolidation_attr_functions.py +0 -0
  483. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_create_release.sh +0 -0
  484. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_custom_components.py +0 -0
  485. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_encoding.py +0 -0
  486. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_equality.py +0 -0
  487. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_error_tolerant_parsing.py +0 -0
  488. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_free_busy_duration.py +0 -0
  489. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_funding_json.py +0 -0
  490. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_ghsa_qjcq_q7h7_r74v_repeat_dos.py +0 -0
  491. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_icalendar.py +0 -0
  492. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_1050_lazy_calendar.py +0 -0
  493. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_1065_new_subcomponents.py +0 -0
  494. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_1066_calendar_uid.py +0 -0
  495. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_1073_pyodide_import.py +0 -0
  496. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_1124_no_utc_vtimezone.py +0 -0
  497. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_1129.py +0 -0
  498. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_116.py +0 -0
  499. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_1226.py +0 -0
  500. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_1231.py +0 -0
  501. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_1237_jcal_paring_of_known_types.py +0 -0
  502. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_1238.py +0 -0
  503. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_127_categories_comma_escaping.py +0 -0
  504. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_1426.py +0 -0
  505. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_1436_implicit_file_read.py +0 -0
  506. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_165_missing_event.py +0 -0
  507. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_168_parsing_invalid_calendars_no_warning.py +0 -0
  508. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_187_type_and_value_do_not_match.py +0 -0
  509. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_218_parse_calendar.py +0 -0
  510. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_279_decoding_categories.py +0 -0
  511. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_27_period.py +0 -0
  512. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_301_add_rrule_as_string.py +0 -0
  513. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_315_uid_required.py +0 -0
  514. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_318_skip_default_parameters.py +0 -0
  515. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_321_dst_offset.py +0 -0
  516. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_322_single_strings_characters_split_into_multiple_categories.py +0 -0
  517. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_336_dateutil_timezone.py +0 -0
  518. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_348_exception_parsing_value.py +0 -0
  519. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_349_value_parameter.py +0 -0
  520. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_350.py +0 -0
  521. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_351_lenient_whitespace_parsing.py +0 -0
  522. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_355_url_escaping.py +0 -0
  523. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_500_vboolean_for_parameter.py +0 -0
  524. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_557_encode_native_parameters.py +0 -0
  525. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_596_calendar_with_attributes.py +0 -0
  526. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_662_component_properties.py +0 -0
  527. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_720_uid_property.py +0 -0
  528. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_722_generate_vtimezone.py +0 -0
  529. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_802.py +0 -0
  530. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_821_stdin_parse.py +0 -0
  531. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_828.py +0 -0
  532. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_836_do_not_quote_tzid.py +0 -0
  533. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_844_timezone_placement.py +0 -0
  534. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_857_enhanced_api.py +0 -0
  535. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_860_improved_setters.py +0 -0
  536. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_864_examples.py +0 -0
  537. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_867_todo_duration_fix.py +0 -0
  538. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_870_vcaladdress_new.py +0 -0
  539. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_884_get_duration.py +0 -0
  540. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_898_todo_end.py +0 -0
  541. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_899_copy_component.py +0 -0
  542. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_950.py +0 -0
  543. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_987.py +0 -0
  544. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_issue_999_negative_event_duration.py +0 -0
  545. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_jcal_recursion.py +0 -0
  546. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_multiple.py +0 -0
  547. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_oss_fuzz_errors.py +0 -0
  548. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_parameter_access.py +0 -0
  549. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_parser_quadratic_unfolding.py +0 -0
  550. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_period.py +0 -0
  551. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_property_params.py +0 -0
  552. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_recurrence.py +0 -0
  553. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_repr_recursion.py +0 -0
  554. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_rfc_6868.py +0 -0
  555. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_rfc_7529.py +0 -0
  556. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_rfc_7953.py +0 -0
  557. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_rfc_7986.py +0 -0
  558. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_rfc_7986_categories.py +0 -0
  559. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_rfc_9074.py +0 -0
  560. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_timezone_identification.py +0 -0
  561. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_timezoned.py +0 -0
  562. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_tools.py +0 -0
  563. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_type_hints.py +0 -0
  564. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_unit_cal.py +0 -0
  565. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/test_with_doctest.py +0 -0
  566. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/timezone_ids.py +0 -0
  567. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/timezones/issue_237_brazilia_standard.ics +0 -0
  568. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/timezones/issue_53_tzid_parsed_properly.ics +0 -0
  569. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/timezones/issue_55_parse_error_on_utc_offset_with_seconds.ics +0 -0
  570. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/timezones/pacific_fiji.ics +0 -0
  571. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tests/todos/example.ics +0 -0
  572. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/timezone/__init__.py +0 -0
  573. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/timezone/equivalent_timezone_ids_result.py +0 -0
  574. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/timezone/provider.py +0 -0
  575. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/timezone/tzid.py +0 -0
  576. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/timezone/zoneinfo.py +0 -0
  577. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/tools.py +0 -0
  578. {icalendar-7.2.2 → icalendar-7.3.2}/src/icalendar/version.py +0 -0
@@ -0,0 +1,16 @@
1
+ {
2
+ "hooks": {
3
+ "UserPromptSubmit": [
4
+ {
5
+ "hooks": [
6
+ {
7
+ "id": "ai-prompt-auto-commit",
8
+ "type": "command",
9
+ "command": "input=$(cat); ts=$(date +%Y-%m-%dT%H-%M-%S); model=$(printf '%s' \"$input\" | jq -r '.model // \"claude-sonnet-4-6\"'); root=$(git rev-parse --show-toplevel 2>/dev/null || pwd); mkdir -p \"$root/.prompts\"; printf '%s' \"$input\" | jq -r '.prompt' > \"$root/.prompts/${ts}_${model}.txt\"",
10
+ "version": "0.0.9"
11
+ }
12
+ ]
13
+ }
14
+ ]
15
+ }
16
+ }
@@ -32,3 +32,5 @@ coverage.xml
32
32
  /ical_fuzzer/
33
33
  # from tutorials
34
34
  /example.ics
35
+ !.claude/
36
+ !.claude/settings.json
@@ -19,6 +19,7 @@ PAPEROPT_letter = -D latex_paper_size=letter
19
19
  ALLSPHINXOPTS = -W -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
20
20
  VALEFILES := $(shell find $(DOCS_DIR) -type f -name "*.rst" -print) # Also add `src` for docstrings.
21
21
  VALEOPTS ?=
22
+ ZIZMOROPTS ?=
22
23
  PYTHONVERSION = >=3.10,<3.15
23
24
 
24
25
  # Add the following 'help' target to your Makefile
@@ -127,6 +128,10 @@ vale: .venv ## Run Vale style, grammar, and spell checks
127
128
  exit 1; \
128
129
  fi
129
130
 
131
+ .PHONY: zizmor
132
+ zizmor: .venv ## Run zizmor static analysis on GitHub Actions workflows
133
+ @uv run zizmor $(ZIZMOROPTS) .github/workflows/
134
+
130
135
  .PHONY: doctest
131
136
  doctest: .venv ## Test snippets and docstrings in the documentation
132
137
  @echo;
@@ -164,6 +169,15 @@ rtd-pr-preview: rtd-prepare .venv ## Build pull request preview on Read the Docs
164
169
  # /deployment
165
170
 
166
171
  # release
172
+ .PHONY: wo
173
+ wo: .venv
174
+ @uv run generate_windows_to_olson_mapping.py
175
+ $(RUFFPATH) format
176
+
177
+ .PHONY: changes-check
178
+ changes-check: dev
179
+ $(TOWNCRIERPATH) check
180
+
167
181
  .PHONY: changes-draft
168
182
  changes-draft: dev
169
183
  @test -n "$(VERSION)" || (echo "VERSION is not set. Run 'export VERSION=x.y.z' first." && exit 1)
@@ -1,10 +1,10 @@
1
- Metadata-Version: 2.4
1
+ Metadata-Version: 2.5
2
2
  Name: icalendar
3
- Version: 7.2.2
3
+ Version: 7.3.2
4
4
  Summary: RFC 5545 compatible parser and generator of iCalendar files
5
5
  Project-URL: Homepage, https://icalendar.readthedocs.io/en/stable/
6
6
  Project-URL: Repository, https://github.com/collective/icalendar
7
- Project-URL: source_archive, https://github.com/collective/icalendar/archive/ad87bcf719fde8088a77c724bc2ae8f09545e0e4.zip
7
+ Project-URL: source_archive, https://github.com/collective/icalendar/archive/3451fdb2104343598322f35cbcfaced590c30489.zip
8
8
  Project-URL: Issues, https://github.com/collective/icalendar/issues
9
9
  Project-URL: Documentation, https://icalendar.readthedocs.io/en/stable/
10
10
  Project-URL: Changelog, https://icalendar.readthedocs.io/en/stable/changelog.html
@@ -140,6 +140,9 @@ Related projects
140
140
  `sphinx-icalendar <https://pypi.org/project/sphinx-icalendar/>`_
141
141
  Provides calendar code blocks and syntax highlighting in a tabbed interface for documentation as an extension to Sphinx.
142
142
 
143
+ `Python Calendaring Ecosystem <https://pycal.org/>`_
144
+ The standards compliant, integrated Python calendar packages.
145
+
143
146
  Change log
144
147
  ==========
145
148
 
@@ -105,6 +105,9 @@ Related projects
105
105
  `sphinx-icalendar <https://pypi.org/project/sphinx-icalendar/>`_
106
106
  Provides calendar code blocks and syntax highlighting in a tabbed interface for documentation as an extension to Sphinx.
107
107
 
108
+ `Python Calendaring Ecosystem <https://pycal.org/>`_
109
+ The standards compliant, integrated Python calendar packages.
110
+
108
111
  Change log
109
112
  ==========
110
113
 
@@ -0,0 +1,4 @@
1
+ - `@geier <https://github.com/geier>`_
2
+ - `@jacadzaca <https://github.com/jacadzaca>`_
3
+ - `@niccokunzmann <https://github.com/niccokunzmann>`_
4
+ - `@SashankBhamidi <https://github.com/SashankBhamidi>`_
@@ -5,7 +5,7 @@
5
5
  },
6
6
  {
7
7
  "name": "7.x (stable)",
8
- "version": "v7.1.3",
8
+ "version": "v7.2.2",
9
9
  "url": "https://icalendar.readthedocs.io/en/stable/",
10
10
  "preferred": true
11
11
  },
@@ -10,10 +10,12 @@ The maintainers of icalendar are grateful for their support.
10
10
  Maintainers
11
11
  -----------
12
12
 
13
- - `@geier <https://github.com/geier>`_
14
- - `@jacadzaca <https://github.com/jacadzaca>`_
15
- - `Nicco Kunzmann <https://github.com/niccokunzmann>`_
13
+ .. include:: ../_include/maintainers.inc
16
14
 
15
+ Documentation lead
16
+ ------------------
17
+
18
+ `@stevepiercy <https://github.com/stevepiercy>`_
17
19
 
18
20
  Original author
19
21
  ---------------
@@ -130,6 +130,38 @@ You can run the following command to automatically format the code.
130
130
  make format
131
131
 
132
132
 
133
+ .. _make-zizmor:
134
+
135
+ Run zizmor
136
+ ----------
137
+
138
+ `zizmor <https://docs.zizmor.sh/>`_ is a static analysis tool for the security of GitHub Actions workflows.
139
+ The command ``make zizmor`` runs the same analysis as the ``zizmor static analysis`` GitHub Actions workflow.
140
+
141
+ .. code-block:: shell
142
+
143
+ make zizmor
144
+
145
+ Pass options to zizmor in the ``ZIZMOROPTS`` environment variable.
146
+ In the following example, generate a SARIF report of the results.
147
+
148
+ .. code-block:: shell
149
+
150
+ make zizmor ZIZMOROPTS="--format sarif"
151
+
152
+ The command ``make zizmor`` automatically installs zizmor into your Python virtual environment when you invoke it the first time.
153
+ If your virtual environment already exists, update it with the following command.
154
+
155
+ .. code-block:: shell
156
+
157
+ make dev
158
+
159
+ .. seealso::
160
+
161
+ - :file:`.github/workflows/zizmor.yml`
162
+ - zizmor's `documentation <https://docs.zizmor.sh/>`_
163
+
164
+
133
165
  Code conventions
134
166
  ----------------
135
167
 
@@ -149,6 +181,8 @@ In addition, "internal use only" objects are not displayed in the documentation.
149
181
  Their docstrings, of course, remain in the Python source code.
150
182
 
151
183
 
184
+ .. _type-hints:
185
+
152
186
  Type hints
153
187
  ''''''''''
154
188
 
@@ -279,11 +279,11 @@ Pull request previews
279
279
  ---------------------
280
280
 
281
281
  On every pull request, Read the Docs generates a pull request preview of the documentation.
282
- It will append a link to the preview in the description of the pull request that the author creates.
282
+ It creates a new comment containing a link to the preview in the pull request.
283
283
 
284
284
  `View all builds of documentation on Read the Docs <https://app.readthedocs.org/projects/icalendar/builds/>`_.
285
285
 
286
- This feature is configured in the file :file:`.readthedocs.yml`.
286
+ This feature is configured in the file :file:`.readthedocs.yml` and the repository settings.
287
287
 
288
288
 
289
289
  .. _continuous-integration-checks:
@@ -76,6 +76,8 @@ Sphinx and its extensions enhance core reStructuredText with additional features
76
76
  For configuration of these features, see :ref:`configure-a-package`.
77
77
 
78
78
 
79
+ .. _markup-examples:
80
+
79
81
  Markup examples
80
82
  ---------------
81
83
 
@@ -282,13 +284,17 @@ The following docstrings items are the most frequently used in icalendar, althou
282
284
 
283
285
  .. important::
284
286
 
285
- When writing docstrings for both a class and its ``__init__`` method, consider the following points.
287
+ Don't write docstrings for a class's ``__init__`` or ``__new__`` methods, if they're present.
288
+ Instead, write a docstring for the class itself.
289
+
290
+ Sphinx will automatically append the ``__init__`` or ``__new__`` docstrings to the class's docstring, which may render the documentation in a confusing manner to the reader.
291
+
292
+ If you find docstrings in a class's ``__init__`` or ``__new__`` methods, then please create a pull request that moves and merges their content into the class's docstring, leaving their docstrings empty.
293
+
294
+ .. seealso::
286
295
 
287
- - A class's docstring must not contain ``Attributes``, ``Parameters``, ``Returns``, or ``Raises`` sections.
288
- - ``Parameters``, ``Returns``, and ``Raises`` sections may be in the ``__init__`` method's docstring.
289
- - The ``__init__`` method's docstring gets automatically appended to its class's docstring by Sphinx.
290
- See :pr:`1164` for an example.
291
- - The one-line summary in the ``__init__`` method's docstring should serve as a narrative bridge from the ending of its class docstring.
296
+ - `Document __new__ methods <https://github.com/collective/icalendar/issues/1118>`_
297
+ - `Merge __init__ or __new__ docstrings into their class's docstring <https://github.com/collective/icalendar/issues/1620>`_
292
298
 
293
299
  Summary
294
300
  Docstrings must begin with a one-line summary of the Python object, terminated by a period.
@@ -304,8 +310,41 @@ Description
304
310
 
305
311
  ``Parameters``
306
312
  Each parameter should consist of its name and a brief description.
307
- You must omit the parameter's type, allowing Sphinx extensions and the use of type hints to automatically render it for you.
308
- This is especially true in a class's ``__init__`` method.
313
+
314
+ Parameters should be sorted, according to the following guidance.
315
+
316
+ - There may be up to two groups of parameters, required and optional.
317
+ - The parameters in the Python signature should retain their existing order, as changing their order may be a breaking change.
318
+ - Required parameters must always appear before optional, both in the Python signature and in the docstring.
319
+ - Within each group of required and optional parameters, sort them in alphabetical order in the docstring.
320
+ - Required attributes should have a term of "Required." in their description, preferably immediately after their name.
321
+
322
+ The following abstraction illustrates a typical example.
323
+
324
+ .. code-block:: python
325
+
326
+ def some_function(creq, breq, areq, bopt=2, aopt=1, copt=3) -> type_hints:
327
+ """Summary.
328
+
329
+ Longer description.
330
+
331
+ Parameters:
332
+ areq: Required. A string.
333
+ breq: Required. A string.
334
+ creq: Required. A string.
335
+ aopt: An integer.
336
+ bopt: An integer.
337
+ copt: An integer.
338
+ """
339
+ pass
340
+
341
+ If the Python signature for a parameter lacks type hints, you must either add :ref:`type hints <type-hints>` or specify the parameter's type manually.
342
+ The Sphinx extensions and the use of type hints automatically render the type for you.
343
+ Using type hints is preferred.
344
+
345
+ .. seealso::
346
+
347
+ :ref:`type-hints`
309
348
 
310
349
  .. note::
311
350
 
@@ -4,14 +4,26 @@ Contribute
4
4
 
5
5
  This guide describes how to contribute to icalendar.
6
6
 
7
+ A key purpose around icalendar is to foster a warm and welcoming space for people to learn, grow, and contribute.
8
+ Contributors in the icalendar community find joy in working with other people and raising them up to contribute again and improve.
9
+
10
+ People in the icalendar community strive to uphold the spirit of the Python Calendaring Ecosystem's `Code of Conduct <https://pycal.org/code-of-conduct/>`_.
11
+ You are invited to read it to help you decide whether you would enjoy being a part of the icalendar community.
12
+
7
13
  Examples of how to contribute
8
14
  -----------------------------
9
15
 
10
16
  - Report security issues per the `Security Policy <https://github.com/collective/icalendar/blob/main/SECURITY.md>`_.
11
17
  - Report all other issues in the `issue tracker <https://github.com/collective/icalendar/issues>`_.
12
18
  - Comment on and resolve issues.
19
+ - Triage open issues and `pull requests <https://github.com/collective/icalendar/pulls>`_.
20
+ - Review, comment on, and make suggestions to change a pull request.
21
+ See the GitHub documentation `Reviewing proposed changes in a pull request <https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request>`_.
13
22
  - Submit pull requests from your fork of the icalendar repository.
14
23
  - Extend the :doc:`documentation/index`.
24
+ - Create or comment on a topic in `Discussions <https://github.com/collective/icalendar/discussions>`_.
25
+ - Write a blog post about icalendar.
26
+ - Share announcements on social media from :doc:`core contributors <credits>` to icalendar.
15
27
  - Sponsor development of icalendar through `Open Collective <https://opencollective.com/python-icalendar>`_.
16
28
 
17
29
 
@@ -69,9 +81,10 @@ Artificial intelligence policy
69
81
  ------------------------------
70
82
 
71
83
  We want to protect the joy, goodwill, and volunteer time of the maintainers and contributors of icalendar.
84
+ Pull request reviewers want to train people, not AI.
72
85
  As such, we take a strong stance against artificial intelligence (AI) abuse.
73
86
 
74
- Contributors to icalendar must follow icalendar's AI policy as described in this section and its subsections.
87
+ Contributors to icalendar must follow icalendar's AI policy as described in this section.
75
88
 
76
89
 
77
90
  .. _responsible-ai-use:
@@ -84,13 +97,25 @@ That means you must comply with :ref:`pull-request-requirements` and follow the
84
97
 
85
98
  If you use AI in your work:
86
99
 
87
- - You must take responsibility for the output, including reviewing and validating the output for accuracy and ensuring it resolves an issue.
88
- - You must check the AI's terms of use, and ensure that outputs are not reconstructed from copyrighted sources.
89
- - You are expected to understand and be able to explain design and code decisions.
100
+ - Before you begin work, you must open an issue per :ref:`issue-requirements`.
90
101
  - In your git commit messages, you must specify both (1) which AI model and version you used, and (2) how you used it, by either including the prompts and interactions you used or summarizing them.
102
+ See the example commit message below.
103
+
104
+ .. code-block:: text
105
+
106
+ Author: Parker Programmer with CodeLLM-3.4 pp@example.org
107
+ Date: Sun Jan 18 10:52:08 2026
108
+ Generate compliance tests
109
+ Prompt: Generate tests for compliance with RFC123 messages.
110
+ Output: (this commit)
111
+
91
112
  You can automate this by using the :program:`ai-prompt-auto-commit` pre-commit hook.
92
113
  See :ref:`AI prompt automation <pre-commit-ai-prompts>` for setup instructions.
93
114
  - You must disclose that you used AI in your change log entry.
115
+ This may be a brief disclosure, not as detailed as the git commit messages, such as, "I used AI to assist me with this change."
116
+ - You must take responsibility for the output, including reviewing and validating the output for accuracy and ensuring it resolves an issue.
117
+ - You must check the AI's terms of use, and ensure that outputs are not reconstructed from copyrighted sources.
118
+ - You are expected to understand and be able to explain design and code decisions.
94
119
  - You shall be held accountable for your AI-generated content.
95
120
 
96
121
 
@@ -116,13 +141,31 @@ The maintainers may close pull requests without providing feedback that they dee
116
141
  The maintainers may also take further action, including suspend, ban, or report GitHub users, as described in Python Calendaring Ecosystem's `Code of Conduct <https://pycal.org/code-of-conduct/>`_.
117
142
 
118
143
 
144
+ .. _issue-requirements:
145
+
146
+ Issue requirements
147
+ ------------------
148
+
149
+ An issue should precede a pull request.
150
+
151
+ When `creating a new issue <https://github.com/collective/icalendar/issues/new/choose>`_, you'll be presented with an issue selector.
152
+ Follow the templates guidance as much as practical.
153
+
154
+ It might be helpful to include an iCalendar file to help reproduce your issue and to use in a test to ensure a bug fix actually resolves your issue.
155
+ To remove private information from an iCalendar file, use :program:`icalendar-anonymizer`, either through its `website <https://icalendar-anonymizer.com/>`_ or install it locally.
156
+ See icalendar-anonymizer's `Installation <https://docs.icalendar-anonymizer.com/latest/installation.html>`_ and documentation for details.
157
+
158
+ Anyone may comment on an issue.
159
+ Discussion of the issue helps collaborators understand its importance and how to resolve it.
160
+
119
161
  .. _pull-request-requirements:
120
162
 
121
163
  Pull request requirements
122
164
  -------------------------
123
165
 
124
- Before submitting your pull request, ensure you have met the following requirements.
166
+ When submitting your pull request, complete the description template on GitHub, and ensure you have met the following requirements.
125
167
 
168
+ #. In your pull request description, link to relevant issues.
126
169
  #. Add a change log entry as described in :ref:`change-log`.
127
170
  This is required and enforced by GitHub checks.
128
171
  #. Add a test which proves your fix and passes.
@@ -135,8 +178,15 @@ The maintainers may also take further action, including suspend, ban, or report
135
178
 
136
179
  .. _change-log:
137
180
 
138
- Change log entry format
139
- ```````````````````````
181
+ Change log requirements
182
+ -----------------------
183
+
184
+ This section describes how to write a change log entry that satisfies the requirements of its :ref:`file name <change-log-file-name>` according to :ref:`types <change-log-types>` and which :ref:`summarizes changes <write-a-good-change-log-entry-label>` in your contribution, including compliance with icalendar's :ref:`responsible-ai-use` policy.
185
+
186
+ .. _change-log-file-name:
187
+
188
+ Change log entry file name
189
+ ``````````````````````````
140
190
 
141
191
  To create a change log entry or news item, create a file in the :file:`news` directory, located in the root of the package.
142
192
 
@@ -170,7 +220,7 @@ The content will still be included in the change log, at the end of the category
170
220
  .. _change-log-types:
171
221
 
172
222
  Change log types
173
- ````````````````
223
+ ~~~~~~~~~~~~~~~~
174
224
 
175
225
  ``breaking``
176
226
  For changes that break the existing API.
@@ -184,6 +234,10 @@ Change log types
184
234
  ``bugfix``
185
235
  For bug fixes and error corrections.
186
236
 
237
+ ``security``
238
+ For security fixes.
239
+ These must go through the `security report protocol <https://github.com/collective/icalendar/blob/main/SECURITY.md>`_.
240
+
187
241
  ``documentation``
188
242
  For changes to the documentation, docstrings, spelling dictionary, or any other documentation matter.
189
243
 
@@ -200,7 +254,7 @@ Change log types
200
254
  .. _write-a-good-change-log-entry-label:
201
255
 
202
256
  Write a good change log entry
203
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
257
+ `````````````````````````````
204
258
 
205
259
  .. important::
206
260
 
@@ -209,7 +263,9 @@ Write a good change log entry
209
263
  The content of this file must include the following.
210
264
 
211
265
  - A brief message that summarizes the changes in your contribution.
212
- - An attribution to yourself, in the format of ``@github_username``.
266
+ - Use :ref:`reStructuredText markup <markup-examples>` to link to relevant RFCs, API usage, and other references.
267
+ - A brief disclosure of AI use, per icalendar's :ref:`responsible-ai-use` policy, if applicable.
268
+ - An attribution to yourself, in the format of ``@github_username``, at the end of the entry.
213
269
 
214
270
  You can write a good change log entry with the following guidance.
215
271
 
@@ -249,6 +305,7 @@ If you would like to set up icalendar to contribute changes, see :doc:`developme
249
305
 
250
306
  documentation/index
251
307
  development
308
+ join-the-icalendar-team
252
309
  code-of-conduct
253
310
  credits
254
311
  maintenance
@@ -0,0 +1,97 @@
1
+ =======================
2
+ Join the icalendar team
3
+ =======================
4
+
5
+ This guide describes how to join the icalendar team.
6
+
7
+
8
+ Purpose
9
+ -------
10
+
11
+ The icalendar team reviews pull requests and issues for quality, makes releases to PyPI, and protects and promotes the icalendar community.
12
+ To familiarize yourself with the icalendar community, read :doc:`index`.
13
+
14
+ To encourage collaboration and community, the icalendar team is actively seeking contributors who are interested in helping to review and triage issues and pull requests.
15
+
16
+ Good candidates for the team demonstrate the following qualifications:
17
+
18
+ - Be friendly, humane, and value diversity and inclusion.
19
+ - Frequently engage with other contributors.
20
+ - Frequently triage and review pull requests and issues.
21
+
22
+
23
+ Members
24
+ -------
25
+
26
+ The members of the icalendar team are listed below under their role.
27
+
28
+
29
+ Maintainers
30
+ ```````````
31
+
32
+ .. include:: ../_include/maintainers.inc
33
+
34
+
35
+ Documentation lead
36
+ ``````````````````
37
+
38
+ `@stevepiercy <https://github.com/stevepiercy>`_
39
+
40
+
41
+ Triage
42
+ ``````
43
+
44
+ Apply to add your name here.
45
+
46
+
47
+ Apply
48
+ -----
49
+
50
+ If you're interested in applying to join the team, you may:
51
+
52
+ - Create a new `Discussion topic <https://github.com/collective/icalendar/discussions/categories/collaborator-nominations>`_ under the Collaborator nominations category.
53
+ - Post a message to the `Matrix icalendar chat <https://matrix.to/#/#pycal:chat.pycal.org>`_.
54
+
55
+ Additionally, the icalendar team may contact you to encourage you to apply.
56
+
57
+ The icalendar team recognizes that many individuals might not feel qualified to apply. Please rest assured that the worst that can happen is that the team will say "not yet, but here's a path you can follow to become qualified." The icalendar team wants to lift people up.
58
+
59
+ The icalendar team values diversity, equity, and inclusion. The icalendar team encourages women, people of color, LGBTQ+ individuals, people with disabilities, neuro-divergent people, members of ethnic minorities, residents of countries outside western culture, people of all ages, and people whose primary language is not English to apply. Members of the icalendar team are committed to building a team that is inclusive of a variety of backgrounds and perspectives.
60
+
61
+
62
+ Elevated access roles
63
+ ---------------------
64
+
65
+ The icalendar team may grant elevated levels of access—what GitHub calls "roles"—to the icalendar repository for contributors based on qualifying criteria.
66
+ GitHub describes `repository roles for an organization
67
+ <https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization#repository-roles-for-organizationswhere>`_ in which it defines access levels.
68
+
69
+ Because icalendar is a public open source software repository, anyone with a GitHub account can perform any action granted by the Read role.
70
+
71
+ The Triage role has the following additional permissions:
72
+
73
+ - Apply and dismiss labels.
74
+ - Close, reopen, and assign all issues and pull requests.
75
+ - Apply milestones.
76
+ - Mark duplicate issues and pull requests.
77
+ - Request pull request reviews.
78
+ - Hide anyone's comments.
79
+ - Move a discussion to a different category.
80
+ - Lock and unlock discussions.
81
+ - Individually convert issues to discussions.
82
+ - Delete a discussion.
83
+
84
+ The primary criteria that the icalendar team uses to consider whether to grant elevated access include, but are not limited to:
85
+
86
+ - Previous contributions to icalendar and related projects, especially pull request reviews and issue triage
87
+ - Previous contributions to other projects
88
+ - Demonstrated understanding of the RFCs and code base without AI assistance
89
+ - Two-factor authentication must be enabled on their GitHub account
90
+ - Strive to uphold the spirit of the Python Calendaring Ecosystem's `Code of Conduct <https://pycal.org/code-of-conduct/>`_
91
+ - Join the `#icalendar Matrix chat <https://matrix.to/#/#pycal:chat.pycal.org>`_
92
+ - Join a video call to get to know each other
93
+
94
+ The icalendar team will review your application, and collect relevant information for evaluation.
95
+
96
+ If the icalendar team determines that you qualify for elevated access, then you'll receive an invitation through an email notification from GitHub to accept.
97
+ If the team determines you're not yet qualified for elevated access, then you'll receive information about next steps to qualify.
@@ -9,10 +9,7 @@ icalendar Maintainers
9
9
 
10
10
  Currently the maintainers are the following people.
11
11
 
12
- - `@geier <https://github.com/geier>`_
13
- - `@jacadzaca <https://github.com/jacadzaca>`_
14
- - `@niccokunzmann <https://github.com/niccokunzmann>`_
15
- - `@SashankBhamidi <https://github.com/SashankBhamidi>`_
12
+ .. include:: ../_include/maintainers.inc
16
13
 
17
14
  Maintainers need the following permissions.
18
15
 
@@ -99,6 +96,14 @@ Adjust the examples for the current release as needed.
99
96
  Since collaborators and maintainers have write access to the repository, they can start the release process.
100
97
  However, only people with ``Environments/Configure PyPI`` access can approve an automated release to PyPI.
101
98
 
99
+ #. Update the Windows to Olson mapping in the :mod:`~icalendar.timezone.windows_to_olson` module.
100
+
101
+ .. code-block:: shell
102
+
103
+ make wo
104
+
105
+ If there are any changes to the module, then open a pull request and merge it.
106
+
102
107
  #. Set an environment variable to use in subsequent commands during the release process.
103
108
 
104
109
  .. code-block:: shell
@@ -353,6 +358,8 @@ Links
353
358
 
354
359
  This section contains useful links for maintainers and collaborators.
355
360
 
361
+ - To remove private information from an iCalendar file for bug reports, use `icalendar-anonymizer <https://github.com/pycalendar/icalendar-anonymizer>`_ either through its `website <https://icalendar-anonymizer.com/>`_ or `install it locally <https://docs.icalendar-anonymizer.com/latest/installation.html>`_.
362
+ - `Python Calendaring Ecosystem <https://pycal.org/>`_
356
363
  - `Future of icalendar, looking for maintainer #360 <https://github.com/collective/icalendar/discussions/360>`_
357
364
  - `Comment on the Plone tests running with icalendar <https://github.com/collective/icalendar/pull/447#issuecomment-1277643634>`_
358
365
 
@@ -94,7 +94,7 @@ One broken property does not prevent access to other valid properties in the sam
94
94
  Round-trip serialization
95
95
  ------------------------
96
96
 
97
- Broken properties preserve their raw values, so they serialize correctly with :meth:`~icalendar.Component.to_ical`.
97
+ Broken properties preserve their raw values, so they serialize correctly with :meth:`Component.to_ical <icalendar.cal.component.Component.to_ical>`.
98
98
 
99
99
  .. code-block:: pycon
100
100
 
@@ -20,6 +20,7 @@ Repology
20
20
  recur.recur
21
21
  reformats
22
22
  RFCs?
23
+ SARIF
23
24
  sphinx_copybutton
24
25
  sphinx_design
25
26
  sphinx_reredirects
@@ -34,3 +35,4 @@ uv
34
35
  vCard
35
36
  xCal
36
37
  Xcode
38
+ zizmor