PACKAGE NAME:  python3-x-wr-timezone-2.0.1-x86_64-1_slackdce.txz
PACKAGE MIRROR:  .
PACKAGE LOCATION:  ./python/python3-x-wr-timezone
PACKAGE SIZE (compressed):  16 K
PACKAGE SIZE (uncompressed):  71 K
PACKAGE REQUIRED:  python3-flit_core,python3-installer,click,python3-dateutil,python3-pyproject-hooks,python3-build,python3-wheel,python3-editables,python3-pathspec,python3-packaging-opt,python3-setuptools-opt,python-zipp,python-importlib_metadata,python3-typing-extensions,python3-setuptools-scm-opt,python3-pluggy,python3-calver,python3-trove-classifiers,python3-hatchling,python3-hatch_vcs,python3-pytz,python3-icalendar,tzdata
PACKAGE CONFLICTS:  
PACKAGE SUGGESTS:  
PACKAGE DESCRIPTION:
python3-x-wr-timezone: python3-x-wr-timezone (Handling of X-WR-TIMEZONE icalendar property)
python3-x-wr-timezone:
python3-x-wr-timezone: Some calendar providers introduce the non-standard X-WR-TIMEZONE
python3-x-wr-timezone: parameter to ICS calendar files. Strict interpretations according to
python3-x-wr-timezone: RFC 5545 ignore the X-WR-TIMEZONE parameter. This causes the times
python3-x-wr-timezone: of the events to differ from those which make use of X-WR-TIMEZONE.
python3-x-wr-timezone:
python3-x-wr-timezone: This module aims to bridge the gap by converting calendars using
python3-x-wr-timezone: X-WR-TIMEZONE to a strict RFC 5545 calendars. So, let's put our
python3-x-wr-timezone: heads together and solve this problem for everyone!
python3-x-wr-timezone: