#20 — DateTime gives up too easily on common US timezones
by
Russ Ferriday
—
last modified
Mar 17, 2009 10:23 PM
| State | Resolved |
|---|---|
| Version: |
—
|
| Area | Functionality |
| Issue type | Bug |
| Severity | Medium |
| Submitted by | Russ Ferriday |
| Submitted on | Mar 17, 2009 |
| Responsible | Maurits van Rees |
| Target release: | 1.0 |
DateTime does not know about EDT or other common US Daylight Saving timezones. There will probably never be a complete low-level fix for this, and any fixes will take ages to agree.
We can try a little harder before giving up and resorting to the warning from Maurits' fix to #18.
We can try a little harder before giving up and resorting to the warning from Maurits' fix to #18.
- Steps to reproduce:
- add
feed://www.businessweek.com/rss/magazine.rss
to a feedfolder.
Today's trunk will show the warnings that Maurits prints as fix to #18.
Added by
Russ Ferriday
on
Mar 17, 2009 09:22 PM
r82643 wraps DateTime calls, traps SyntaxErrors thrown, and performs a lookup for the additional timezones. Only if this fails or the timezone is found and the syntax is still intractible is the SyntaxError raised.
Added by
Maurits van Rees
on
Mar 17, 2009 10:23 PM
Hi Russ.
Issue state:
Unconfirmed
→
Resolved
Responsible manager:
(UNASSIGNED)
→
maurits
Target release:
None
→
1.0
This should ideally be in the Zope DateTime module. But that is apparently very tricky, as can be seen here:
https://bugs.launchpad.net/zope2/+bug/142148
http://regebro.wordpress.com/[…]/
http://regebro.wordpress.com/[…]/
For now this looks okay, and the tests run on my machine too, so thanks for the fix.
I did add to todo item in r82651 stating that we want to get rid of this hack eventually. :-)
No responses can be added.
If you can, please log in before submitting a reaction.
