On Sun, 30 Sep 2012 21:55:34 +0300 Serhiy Storchaka <storchaka at gmail.com> wrote: > On 30.09.12 16:15, Antoine Pitrou wrote: > > Probably, but for most purposes I would guess a 2-year old database is > > still good enough? After all, you don't see many people complaining > > about the outdated Unicode database that is hard-wired in past Pythons. > > In 2011 Ukrainian timezone data was changed twice for year. And perhaps > even change in 2013. Russian timezones were changed over the last few > years and most likely will change in the near future. Correct time is > critical for many applications. Perhaps, but that's the responsibility of governements. Just because some governments have erratic policies shouldn't be a reason for residents of other countries not to enjoy the benefits of their stable timezones. Regards Antoine. -- Software development and contracting: http://pro.pitrou.net
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4