On 2012-09-30 19:55, Serhiy Storchaka 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. > That's what UTC is for! :-) I think that it would be a good idea to provide a database with the release plus a tool for updating it, the updates being announced by email or RSS, and the ability to use the system's database if there's one.
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