-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Amos Latteier wrote:
Andreas Jung wrote:
I would not care much about dropping the support for "weird timezone names" without further notice as long as their is an easy way for people migrating their code e.g. by specifying a proper tz name.
I should clarify that they are mostly abbreviations.
I also agree with Lennart Regebro, that the correct solution is to replace DateTime with datetime, and so it's not worth breaking too much.
I think consensus here is that the DateTIme stuff has BBB contracts which are literally unbreakable: - millions of pickles are out there in ZODB land which will barf if DateTime doesn't preserve existing semantics. - Bunches of third-party application code uses the DateTime API, in particular the DWIMish constructor. I think your change (using pytz to handle timezones, with fallback to the older code) is a sensible compromise. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHBSXU+gerLs4ltQ4RAp0hAJ9YAKnuSkYGBMLG9zEK/qoLv6VMHwCfbXgJ XkIPQNsmCgRHRlmExFhMk9E= =ki/q -----END PGP SIGNATURE-----