[Python-Dev] Draft PEP for time zone support. (original) (raw)

Paul Moore p.f.moore at gmail.com
Wed Dec 12 09:13:16 CET 2012

On 12 December 2012 00:58, Nick Coghlan <ncoghlan at gmail.com> wrote:

I'd prefer a more aggressive name for this like "tzdataoverride". My rationale is that *nix users need to thoroughly aware that if they install this package, they will stop benefiting from the automatic tz database updates provided by their OS (especially if they install it into the system site packages on a distro that has migrated to Python 3 for system tools).

Such a name would also make it possible to provide two packaged databases, one checked before the OS data (tzdataoverride), and one shipped with Python itself that is used only if the OS doesn't provide the timezone database (tzdatafallback). tzdatafallback would then be updated to the latest Olsen database for each maintenance release. Cross-platform applications that wanted more reliably up to date timezone data could then conditionally depend on tzdataoverride for Windows deployments (using the environment marker support in metadata 1.2+).

That sounds sensible, EIBTI and all that. It is a lot simpler than shipping the package and some sort of auto-updater, too.

Paul

More information about the Python-Dev mailing list