On Thu, Feb 18, 2010 at 03:48, Michael Foord <fuzzy...@voidspace.org.uk> wrote: > Some of the Linux distributions *already* patch pytz to use the system > information, which they keep updated separately.
Yes. And what problem does including pytz in the stdlib solve? > That information is also > available from the system on Mac OS and Windows. It is not available on Windows in any reasonable and useable form. > It would seem to be very > useful to have a version of pytz that defaults to using the system > information if available, has a mechanism for using separate data for > systems that don't provide the information or raises an error when neither > system information nor separate data is available. Pytz has mechanisms for that, perhaps they should be more easily useable. Perhaps it should even default to using the system Olsen database if there is one. But the discussion was if it should be included in the standard library, and nobody still has explain what problem that would solve. If it doesn't solve a problem, it shouldn't be done, as it also is going to create problems, because everything does. :) > The data could then still be available and released regularly without being > tied to the Python release schedule. Which it already is. So.... no problem solved. -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64 _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com