Some calendar creators such as Google Calendar
introduce the non-standard X-WR-TIMEZONE
parameter
to ICS calendar files to change the timezone.
Strict interpretations according to RFC 5545 ignore the X-WR-TIMEZONE
parameter.
This causes the times of the events to differ from those
which make use of X-WR-TIMEZONE
.
This module aims to bridge the gap by converting calendars
using X-WR-TIMEZONE
to a strict RFC 5545 calendars.
So, let's put our heads together and solve this problem for everyone!
Some features of the module are:
- Easy install with Python's
pip
. - Command line conversion of calendars.
- Piping of calendar files with
wget
orcurl
.
Some of the requirements are:
- Calendars without
X-WR-TIMEZONE
are kept unchanged. - Passing calendars twice to this module does not change them.
Install using pip
:
python3 -m pip install x-wr-timezone
Install with apt
:
sudo apt-get install python-x-wr-timezone
You can standardize the calendars using your command line interface.
The examples assume that in.ics
is a calendar which may use
X-WR-TIMEZONE
, whereas out.ics
does not require X-WR-TIMEZONE
for proper display.
cat in.is | x-wr-timezone > out.ics
x-wr-timezone in.ics out.ics
curl https://example.org/in.ics | x-wr-timezone > out.ics
wget -O- https://example.org/in.ics | x-wr-timezone > out.ics
You can get usage help on the command line:
x-wr-timezone --help
After you have installed the library, you can import it.
import x_wr_timezone
The function to_standard()
converts an icalendar
object.
x_wr_timezone.to_standard(an_icalendar)
Here is a full example which does about as much as this module is supposed to do:
import icalendar # installed with x_wr_timezone
import x_wr_timezone
with open("in.ics", 'rb') as file:
calendar = icalendar.from_ical(file.read())
new_calendar = x_wr_timezone.to_standard(calendar)
# you could use the new_calendar variable now
with open('out.ics', 'wb') as file:
file.write(new_calendar.to_ical())
to_standard(calendar, timezone=None)
has these parameters:
calendar
is theicalendar.Calendar
object.timezone
is an optional time zone. By default, the time zone incalendar['X-WR-TIMEZONE']
is used to check if the calendar needs changing. Whentimezone
is notNone
however,calendar['X-WR-TIMEZONE']
will not be tested and it is assumed that thecalendar
should be changed as ifcalendar['X-WR-TIMEZONE']
had the value oftimezone
. This does not add or change the value ofcalendar['X-WR-TIMEZONE']
. You would need to do that yourself.timezone
can be a string like"UTC"
or"Europe/Berlin"
or apytz.timezone
or something thatdatetime
accepts as a time zone..- Return value: The
calendar
argument is not modified at all. The calendar returned has the attributes and subcomponents of thecalendar
only changed and copied where needed to return the proper value. As such, the returned calendar might be identical to the one passed to the function as thecalendar
argument. Keep that in mind if you modify the return value.
Clone the repository or its fork and
cd x-wr-timezone
.Optional: Install virtualenv and Python3 and create a virtual environment:
pip install virtualenv virtualenv -p python3 ENV source ENV/bin/activate # you need to do this for each shell
Install the packages and this module so it can be edited:
pip install -r test-requirements.txt -e .
Run the tests:
pytest
To test all functions:
pytest --x-wr-timezone all
You can use tox
to test the package in different Python versions.
tox
This tests all the different functionalities:
tox -- --x-wr-timezone all
To release new versions,
edit the Changelog Section
edit setup.py, the
__version__
variablecreate a commit and push it
Wait for CI tests to finish the build.
run
python3 setup.py tag_and_deploy
notify the issues about their release
If you need to add or remove a Python version, you need to modify these files:
- ... README.rst in the changelog section
- ... setup.py
- ... tox.ini
- ... tests.yml
This project's development is driven by tests. Tests assure a consistent interface and less knowledge lost over time. If you like to change the code, tests help that nothing breaks in the future. They are required in that sense. Example code and ics files can be transferred into tests and speed up fixing bugs.
You can view the tests in the test folder.
If you have a calendar ICS file for which this library does not
generate the desired output, you can add it to the test/calendars
folder and write tests for what you expect.
If you like, open an issue first, e.g. to discuss the changes and
how to go about it.
- v1.0.2
- Added support for Python 3.13
- v1.0.1
- Use zoneinfo instead of pytz
- Test compatibility with pytz and zoneinfo as argument to to_standard
- Remove pytz as a dependency
- Add tzdata as a dependency
- Add typing
- Update Python versions
- v0.0.7
- Rename master branch to main
- Use proper SPDX license ID
- Test Python 3.12
- v0.0.6
- Obsolete Python 3.7
- Support Python 3.11
- Fix localization issue for pytz when datetime has no timezone
- Run tests on GitHub Actions
- Require icalendar 5.0.11 for tests
- Fix pytz localization issue when dateime is not in UTC and has no time zone.
- v0.0.5
- Revisit README and CLI and fix spelling mistakes.
- Modified behavior to treat events without time zone found in a calendar using the X-WR-TIMEZONE property, see Pull Request 7
- v0.0.4
- Test automatic deployment with Gitlab CI.
- v0.0.3
- Use
tzname()
function ofdatetime
to test for UTC. This helps support zoneinfo time zones. - Split up visitor class and rename it to walker.
- Use
- v0.0.2
- Implement the
timezone
argument. - Do not modify the value of the
calendar
argument and only copy it where needed.
- Implement the
- v0.0.1
- Initial release supports DTSTART, DTEND, EXDATE, RDATE, RECURRENCE-ID attributes of events.
- Command line interface as
x-wr-timezone
.
This module was reated beause of these issues:
This module uses the icalendar
library for parsing calendars.
This library is used by python-recurring-ical-events
to get events at specific dates.
This software is licensed under LGPLv3, see the LICENSE file.