[Zope-dev] Zope Tests: 5 OK

2007-10-30 Thread Zope Tests Summarizer 
Summary of messages to the zope-tests list.
Period Mon Oct 29 13:00:00 2007 UTC to Tue Oct 30 13:00:00 2007 UTC.
There were 5 messages: 5 from Zope Unit Tests.


Tests passed OK
---

Subject: OK : Zope-2.7 Python-2.3.6 : Linux
From: Zope Unit Tests
Date: Mon Oct 29 21:47:16 EDT 2007
URL: http://mail.zope.org/pipermail/zope-tests/2007-October/008566.html

Subject: OK : Zope-2.8 Python-2.3.6 : Linux
From: Zope Unit Tests
Date: Mon Oct 29 21:48:47 EDT 2007
URL: http://mail.zope.org/pipermail/zope-tests/2007-October/008567.html

Subject: OK : Zope-2.9 Python-2.4.4 : Linux
From: Zope Unit Tests
Date: Mon Oct 29 21:50:17 EDT 2007
URL: http://mail.zope.org/pipermail/zope-tests/2007-October/008568.html

Subject: OK : Zope-2.10 Python-2.4.4 : Linux
From: Zope Unit Tests
Date: Mon Oct 29 21:51:47 EDT 2007
URL: http://mail.zope.org/pipermail/zope-tests/2007-October/008569.html

Subject: OK : Zope-trunk Python-2.4.4 : Linux
From: Zope Unit Tests
Date: Mon Oct 29 21:53:17 EDT 2007
URL: http://mail.zope.org/pipermail/zope-tests/2007-October/008570.html

___
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 )

[Zope-dev] Re: SVN: Zope/trunk/lib/python/DateTime/tests/testDateTime.py Fix test. According to http://en.wikipedia.org/wiki/ISO_8601

2007-10-30 Thread Laurence Rowe 

Andreas Jung wrote:



--On 27. Oktober 2007 18:01:25 -0400 Tres Seaver [EMAIL PROTECTED] 
wrote:




   DateTime('2006-01-01')._tz
  'US/Eastern'


Yeah, that's completely odd.


But standards compliant. The previous behaviour was contrary to the 
specification. 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.






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.


Totally agreed.


However if we must preserve this bug for backwards compatibility then we 
must. (This bugfix would not change the interpretation of existing pickles).





(http://www.zope.org/Collectors/Zope/2109),


Is this right issue? The URL redirection to LP points me to this:

https://bugs.launchpad.net/zope2/+bug/143701



The trunk should be reverted to preserve the old behavior, which may be
relied on by third-party applications.


Jup, either revert the change or fix it.

Andreas


'Fixed' in r81213.

Laurence

___
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 )

[Zope-dev] buildbot failure in Zope trunk 2.4 Windows 2000 zc-bbwin6

2007-10-30 Thread buildbot 
The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 
zc-bbwin6.

Buildbot URL: http://buildbot.zope.org/

Build Reason: changes
Build Source Stamp: 2882
Blamelist: 
amos,andreasjung,baijum,faassen,fdrake,hannosch,icemac,jim,jukart,ldr,philikon,srichter,wichert

BUILD FAILED: failed svn

sincerely,
 -The Buildbot

___
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 )

[Zope-dev] buildbot failure in Zope trunk 2.4 Windows 2000 zc-bbwin6

2007-10-30 Thread buildbot 
The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 
zc-bbwin6.

Buildbot URL: http://buildbot.zope.org/

Build Reason: changes
Build Source Stamp: 2883
Blamelist: ldr

BUILD FAILED: failed svn

sincerely,
 -The Buildbot

___
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 )

[Zope-dev] Re: SVN: Zope/trunk/lib/python/DateTime/tests/testDateTime.py Fix test. According to http://en.wikipedia.org/wiki/ISO_8601

2007-10-30 Thread Tres Seaver 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Laurence Rowe wrote:
 Andreas Jung wrote:

 --On 27. Oktober 2007 18:01:25 -0400 Tres Seaver [EMAIL PROTECTED] 
 wrote:


DateTime('2006-01-01')._tz
   'US/Eastern'
 Yeah, that's completely odd.
 
 But standards compliant. The previous behaviour was contrary to the 
 specification. 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.

When your users are scattered across the internet, there *is* no single
cnventional local time which will not surprise some / most of them;  the
timezone of the location in which the server happens to reside is
completely irrelevant to a user.

Zope has therefore adopted the convention that local time in Zope is
GMT for ISO-spelled strings (the slash form uses the OS-supplied
default timezone, again for backward-compatibility;  the ISO spelling
was added later).

 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.
 Totally agreed.
 
 However if we must preserve this bug for backwards compatibility then we 
 must. (This bugfix would not change the interpretation of existing pickles).

The issue is not about pickles, but about code, and user interfaces,
whose meanings have changed.

 (http://www.zope.org/Collectors/Zope/2109),
 Is this right issue? The URL redirection to LP points me to this:

 https://bugs.launchpad.net/zope2/+bug/143701

 The trunk should be reverted to preserve the old behavior, which may be
 relied on by third-party applications.
 Jup, either revert the change or fix it.

 Andreas
 
 'Fixed' in r81213.

Thank you.


Tres.
- --
===
Tres Seaver  +1 540-429-0999  [EMAIL PROTECTED]
Palladion Software   Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHJ6Zq+gerLs4ltQ4RAomIAJ0fcczrGkXCc2CY0I9VEFxdNSyi5wCg0i/z
IR+DvtM0eVL7kWol55+H/m8=
=sBPV
-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 )