-
-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transition from pytz to zoneinfo #609
Labels
nlnet
Development is funded by NLNet & NGI Zero Core https://nlnet.nl/project/OpenWebCalendar
Comments
niccokunzmann
added
the
nlnet
Development is funded by NLNet & NGI Zero Core https://nlnet.nl/project/OpenWebCalendar
label
Apr 10, 2024
Open
25 tasks
Also:
For a new release:
|
I created #623 to work on some improvements. |
This is complete. We do not depend on pytz any more. 🥳 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
nlnet
Development is funded by NLNet & NGI Zero Core https://nlnet.nl/project/OpenWebCalendar
In EOL of Python 3.8 is 31st October 2024. Then, zoneinfo is the library that is shipped with Python. There are problems using pytz as timezone implementations have evolved. My proposal to solve this issue is the following:
icalendar.set_default_timezone_implementation(TimeZone)
whereTimeZone
can be pytz.Timezone or zoneinfo.ZoneInfo or others, taking a string like"UTC"
orEurope/Berlin
.What are your thoughts? Who thinks this will break existing code? What is needed for a transition?
See also:
Possibly related:
Code that needs touching:
The Timezone class contains logic to parse and create timezones from icalendar specifications:
icalendar/src/icalendar/cal.py
Line 545 in 2b1cd4e
The text was updated successfully, but these errors were encountered: