On 5 Aug 2006, at 22:38, Dieter Maurer wrote:
Florent Guillaume wrote at 2006-8-5 00:17 +0200:
Stuart Bishop wrote:
...
I've been wondering if making pytz work like this was a correct
decision. It
seems that people who know enough to care about DST transition
periods
generally work in UTC anyway
What makes you say that? Any application where datetimes are
user-entered and user-visible will certainly *not* want to store
them in
UTC, as users will want dates displayed "as they were
entered" (meaning
holding their original timezone, even if the timezone is not
displayed).
*nix recommends to store the time in UTC (in the hardware clock).
Nevertheless, users see and can enter the time in their local
timezone.
Unix has nothing to do with an application manipulating proper
calendaring concepts. The original timezone information can be quite
important, and the local timezone of the user seeing the information
may not be the appropriate one.
This demonstrates that the storage format can be independent of what
the user sees or enters...
Provided all you want is store an instant in time. Which is only a
limited subset of what can be useful in general.
Florent
--
Florent Guillaume, Nuxeo (Paris, France) Director of R&D
+33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED]
_______________________________________________
Zope3-dev mailing list
[email protected]
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
