This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/11620] Bad design of timezone conversions
- From: "maxim.yegorushkin at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Fri, 09 Nov 2012 00:23:00 +0000
- Subject: [Bug libc/11620] Bad design of timezone conversions
- Auto-submitted: auto-generated
- References: <bug-11620-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=11620
--- Comment #4 from Maxim Yegorushkin <maxim.yegorushkin at gmail dot com> 2012-11-09 00:23:00 UTC ---
...
Because of the lack of this functionality in glibc there is a proliferation of
different tzdata copies in Linux. Python's pytz comes with a copy, ICU with
another one, to name a few.
Worst case scenario is that an application using one copy of tzdata talks to
another application using another copy of tzdata using non-local timezone
timestamps. tzdata mismatch can lead to unexpected behaviour, especially for
recent dates if one library has upgraded to the latest tzdata when the other
hasn't. (This problem, though, is inherent in web applications served by
different hosts, which can't be reasonably expected to have tzdata in-sync,
hence to mitigate the problem they must only talk UTC).
Different hosts aside, keeping just one copy of tzdata on a system feels to be
also a sensible idea.
Okay, I will try to keep trolling down now...
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.