Currently switching to DST and back is done by hand twice a year by editing the config files. This causes confusion if the edit is missed by a few days, or if events have been created for times both before and after the DST change. After making events timezone-aware in #97, they could automatically show the correct DST/non-DST timezone.
Python seems to support DST natively to some extent. There is also the pytz package.
Currently switching to DST and back is done by hand twice a year by editing the config files. This causes confusion if the edit is missed by a few days, or if events have been created for times both before and after the DST change. After making events timezone-aware in #97, they could automatically show the correct DST/non-DST timezone.
Python seems to support DST natively to some extent. There is also the
pytz
package.