-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Laurence Rowe wrote:
> Log message for revision 80922:
> Fix test. According to http://en.wikipedia.org/wiki/ISO_8601
> If no time zone information is given with a time, the time zone is assumed
> to be in some conventional local time zone.
If I understand correctly, the trunk has had a BBB-incompatible change
to the semantics of the DateTime constructor:
In Zope 2.10.x (as well as 2.9x, 2.8x, and 2.7x):
>>> from DateTime.DateTime import DateTime
>>> DateTime('2006/01/01')._tz
'US/Eastern'
>>> DateTime('2006/01/01 UTC')._tz
'Universal'
>>> DateTime('2006-01-01')._tz
'GMT+0'
On the trunk:
>>> from DateTime.DateTime import DateTime
>>> DateTime('2006/01/01')
DateTime('2006/01/01')
>>> DateTime('2006/01/01')._tz
'US/Eastern'
>>> DateTime('2006/01/01 UTC')._tz
'UTC'
>>> DateTime('2006-01-01')._tz
'US/Eastern'
I strongly disagreed with the argument for that change
(http://www.zope.org/Collectors/Zope/2109), because it broke the
semantics of the class, based on long-established use in Zope: datetime
strings which used ISO notation, but provided no explicit timezone, were
assigned 'GMT+0' as the timezone.
The trunk should be reverted to preserve the old behavior, which may be
relied on by third-party applications.
Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
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
iD8DBQFHI7U1+gerLs4ltQ4RAraFAJwKFa2DOCYn3dPzBM8jXnlajEcrpACeKalL
BxeHK/EzDNqV5tT0yY0J76I=
=HL8g
-----END PGP SIGNATURE-----
_______________________________________________
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
