Opened 6 years ago
Closed 6 years ago
#116 closed defect (fixed)
Timetables on ''Canada/Eastern" fail to generate
Reported by: | pferreir | Owned by: | pferreir |
---|---|---|---|
Priority: | normal | Milestone: | v0.97.0 |
Component: | General | Version: | 0.97.0 |
Keywords: | Cc: |
Description (last modified by pferreir)
Example: http://indicobeta.cern.ch/conferenceDisplay.py?confId=78302
In [28]: c.getSchedule().getAdjustedStartDate(c.getTimezone()) Out[28]: datetime.datetime(2010, 1, 8, 17, 30, tzinfo=<UTC>) In [29]: c2.getSchedule().getAdjustedStartDate(c2.getTimezone()) Out[29]: datetime.datetime(2010, 9, 17, 8, 0, tzinfo=<DstTzInfo 'Europe/Zurich' CEST+2:00:00 DST>) In [31]: c.getTimezone() Out[31]: 'Canada/Eastern' In [32]: c2.getTimezone() Out[32]: 'Europe/Zurich'
Change History (6)
comment:1 Changed 6 years ago by pferreir
- Owner set to pferreir
- Status changed from new to accepted
comment:2 Changed 6 years ago by pferreir
- Description modified (diff)
comment:3 Changed 6 years ago by pferreir
comment:4 Changed 6 years ago by pferreir
... we need not only to fix this by either removing the constraint or allowing the user to select only from common_timezones, but also to make sure normalizing the timetable generates for UTC events (since UTC is allowed as a valid timezone).
comment:5 Changed 6 years ago by admin
- Milestone set to v0.97
- Version set to 0.97
comment:6 Changed 6 years ago by pferreir
- Resolution set to fixed
- Status changed from accepted to closed
Pytz 2010b apparently fixes this.
Thanks, Stuart.
Note: See
TracTickets for help on using
tickets.
OK, it seems this is causing the problem (conference.py:
Notice how tz is set as 'UTC' if the timezone is not in common_timezones. That's the case for Canada/Eastern...