[Python-Dev] Stdlib and timezones, again (original) (raw)

Tres Seaver tseaver at palladion.com
Mon Oct 1 20:23:30 CEST 2012


-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 10/01/2012 10:12 AM, Antoine Pitrou wrote:

On Mon, 1 Oct 2012 16:06:18 +0200 Lennart Regebro <regebro at gmail.com> wrote:

Actually, that's not a bad idea. My original idea was to warn if it was outdated, but since there is no way to check that, I scratched that idea. But as I have pointed out several times, a database that is shipped with Python is almost guaranteed to be outdated, so yeah, we could just warn all the time. :-)

I like this idea. It gives an incentive to update: Get rid of the annoying warning. Well, no, it is just silly. If we ship a database, that's because we think it is good enough. A warning is just a nuisance here. We don't display warnings when the installed Python version is too old.

Using a bundled version would be the Wrong Thing (TM) for almost any non-toy application (one where non-programmers actually care about the timezones in which dates / times are entered / displayed): the fact that the errors would infrequent / subtle / hard to diagnose is an argument against inclusion.

Tres. - --

Tres Seaver +1 540-429-0999 tseaver at palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEUEARECAAYFAlBp36IACgkQ+gerLs4ltQ4mbACY60cQ1SbUgRh0hNtUmxScRM68 ZwCg125QzeMmhFV0VYYZGmNVmEqpajo= =ehg8 -----END PGP SIGNATURE-----



More information about the Python-Dev mailing list