Re: [Zope-dev] Zope Tests: 72 OK, 15 Failed

2011-02-21 Thread Jan-Jaap Driessen
Hi Marius,

On 18 February 2011 17:34, Marius Gedminas mar...@gedmin.as wrote:
 On Fri, Feb 18, 2011 at 09:21:12AM +0100, Jan-Jaap Driessen wrote:
 Thank you for looking into this. I am kind of happy that the error can
 be reproduced on a different windows machine.

 Tres,

 It is indeed 'special' that this error occurs only now. The windows
 builds for zope.dublincore trunk have not shown this error:

 http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_3%20slave-win
 http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_5%20slave-win
 http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_trunk%20slave-win

 How to proceed? Make the regex in
 zope.dublincore.tests.test_timeannotators less strict?

 That sounds like the right solution to me.

 I am not a pypi owner of zope.dublincore,

 I am.  Would you like to be too?

 Marius Gedminas

Thanks for looking into this. I was away from my computer for a while
and couldn't get back to you before. I see that Tres fixed
zope.dublincore in the mean time.

Cheers,

-- 
Jan-Jaap Driessen
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 72 OK, 15 Failed

2011-02-19 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/18/2011 04:47 PM, Tres Seaver wrote:

 zope.dublincore.tests.test_timeannotators less strict?
 
 I am not a pypi owner of zope.dublincore, so Tres, could you do the honors?
 
 I made a stab at fixing the regex.  If the dev checkouts start
 passing, then we can do a release.

I tagged a 3.8.2 release and pushed it to PyPI.


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

iEYEARECAAYFAk1fzSUACgkQ+gerLs4ltQ6kXACgpN57yImuKB0JOs8or9aKoR7Z
0GYAoJxAy792QR0vRNnSvhKbEgsQU5a9
=HU1i
-END PGP SIGNATURE-

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 72 OK, 15 Failed

2011-02-18 Thread Jan-Jaap Driessen
On 18 February 2011 00:55, Simon Elbaz elbazsim...@gmail.com wrote:
 Hi,
 I have tried this code on Python 2.7.1 (r271:86832, Nov 27 2010, 18:30:46)
 [MSC v.1500 32 bit (Intel)] on win32. It seems that it is possible to have
 no milliseconds returned by datetime.now.

 while 1:
 ...     datetime.now(pytz.utc)
 datetime.datetime(2011, 2, 17, 23, 48, 17, 984000, tzinfo=UTC)
 datetime.datetime(2011, 2, 17, 23, 48, 17, 984000, tzinfo=UTC)
 datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
 datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
 datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
 ...
 datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
 datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
 ...
 datetime.datetime(2011, 2, 17, 23, 48, 18, 15000, tzinfo=UTC)
 datetime.datetime(2011, 2, 17, 23, 48, 18, 15000, tzinfo=UTC)
 datetime.datetime(2011, 2, 17, 23, 48, 18, 15000, tzinfo=UTC)
 datetime.datetime(2011, 2, 17, 23, 48, 18, 125000, tzinfo=UTC)
 Traceback (most recent call last):
   File stdin, line 2, in module
   File
 C:\Python27\lib\site-packages\pytz-2011b-py2.7.egg\pytz\__init__.py, li
 ne 186, in utcoffset
 KeyboardInterrupt


 Simon

 On Thu, Feb 17, 2011 at 4:58 PM, Tres Seaver tsea...@palladion.com wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 02/17/2011 06:58 AM, Zope Tests Summarizer wrote:

  Subject: FAILED : Zope Buildbot / zopetoolkit-1.1_win-py2.5 slave-win
  From: jdriessen at thehealthagency.com
  Date: Wed Feb 16 15:03:12 EST 2011
  URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032218.html
 
  Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.5 slave-win
  From: jdriessen at thehealthagency.com
  Date: Wed Feb 16 15:18:08 EST 2011
  URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032223.html
 
  Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.6 slave-win
  From: jdriessen at thehealthagency.com
  Date: Wed Feb 16 15:25:31 EST 2011
  URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032226.html

 These three failures are due to a quirk in how datetime.datetime repr
 works:  if the 'microseconds' field happens to be zero, it isn't
 printed, e.g.:

 Expected:
    datetime.datetime(DATETIME, tzinfo=UTC)
 Got:
    datetime.datetime(2011, 2, 16, 20, 0, 43, tzinfo=UTC)

 The regex (in zope.dublincore.tests.test_timeannotators), expects the
 microseconds value to be present:

  datetime_re = (
     '[0-9]{4}, [0-9]{1,2}, [0-9]{1,2}, [0-9]{1,2}, [0-9]{1,2}, \
     [0-9]{1,2}, '
    '[0-9]{1,6}')


 I have no idea why that value is suddenly exactly zero for the THA box.


 Tres.

Simon,

Thank you for looking into this. I am kind of happy that the error can
be reproduced on a different windows machine.

Tres,

It is indeed 'special' that this error occurs only now. The windows
builds for zope.dublincore trunk have not shown this error:

http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_3%20slave-win
http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_5%20slave-win
http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_trunk%20slave-win

How to proceed? Make the regex in
zope.dublincore.tests.test_timeannotators less strict?

I am not a pypi owner of zope.dublincore, so Tres, could you do the honors?

Jan-Jaap
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 72 OK, 15 Failed

2011-02-18 Thread Adam GROSZER
Hello,

On Thu, 17 Feb 2011 10:58:35 -0500 you wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 02/17/2011 06:58 AM, Zope Tests Summarizer wrote:

 Subject: FAILED : Zope Buildbot / zopetoolkit-1.1_win-py2.5 slave-win
 From: jdriessen at thehealthagency.com
 Date: Wed Feb 16 15:03:12 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032218.html

 Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.5 slave-win
 From: jdriessen at thehealthagency.com
 Date: Wed Feb 16 15:18:08 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032223.html

 Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.6 slave-win
 From: jdriessen at thehealthagency.com
 Date: Wed Feb 16 15:25:31 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032226.html

 These three failures are due to a quirk in how datetime.datetime repr
 works:  if the 'microseconds' field happens to be zero, it isn't
 printed, e.g.:

 Expected:
  datetime.datetime(DATETIME, tzinfo=UTC)
 Got:
  datetime.datetime(2011, 2, 16, 20, 0, 43, tzinfo=UTC)

 The regex (in zope.dublincore.tests.test_timeannotators), expects the
 microseconds value to be present:

   datetime_re = (
   '[0-9]{4}, [0-9]{1,2}, [0-9]{1,2}, [0-9]{1,2}, [0-9]{1,2}, \
   [0-9]{1,2}, '
  '[0-9]{1,6}')


 I have no idea why that value is suddenly exactly zero for the THA box.

Windowze... We also have such a failure 1 in 50 buildbot runs.
Tho very misterious how it could happen 3x in a row.

-- 
Best regards,
  Adam GROSZER
--
Quote of the day:
Faith on a full stomach may be simply contentment- but if you have it 
when you're hungry, it's genuine.
- Frank A. Clark
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 72 OK, 15 Failed

2011-02-18 Thread Martijn Pieters
On Fri, Feb 18, 2011 at 10:39, Adam GROSZER agroszer...@gmail.com wrote:
 Windowze... We also have such a failure 1 in 50 buildbot runs.
 Tho very misterious how it could happen 3x in a row.

If the failure is random, with a chance of 1 in 50, 3 times in a row
is no mystery. It shows the failure is truly random! :-)

-- 
Martijn Pieters
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 72 OK, 15 Failed

2011-02-18 Thread Marius Gedminas
On Fri, Feb 18, 2011 at 09:21:12AM +0100, Jan-Jaap Driessen wrote:
 Thank you for looking into this. I am kind of happy that the error can
 be reproduced on a different windows machine.
 
 Tres,
 
 It is indeed 'special' that this error occurs only now. The windows
 builds for zope.dublincore trunk have not shown this error:
 
 http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_3%20slave-win
 http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_5%20slave-win
 http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_trunk%20slave-win
 
 How to proceed? Make the regex in
 zope.dublincore.tests.test_timeannotators less strict?

That sounds like the right solution to me.

 I am not a pypi owner of zope.dublincore,

I am.  Would you like to be too?

Marius Gedminas
-- 
http://pov.lt/ -- Zope 3/BlueBream consulting and development


signature.asc
Description: Digital signature
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 72 OK, 15 Failed

2011-02-18 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/18/2011 03:21 AM, Jan-Jaap Driessen wrote:
 On 18 February 2011 00:55, Simon Elbaz elbazsim...@gmail.com wrote:
 Hi,
 I have tried this code on Python 2.7.1 (r271:86832, Nov 27 2010, 18:30:46)
 [MSC v.1500 32 bit (Intel)] on win32. It seems that it is possible to have
 no milliseconds returned by datetime.now.

 while 1:
 ... datetime.now(pytz.utc)
 datetime.datetime(2011, 2, 17, 23, 48, 17, 984000, tzinfo=UTC)
 datetime.datetime(2011, 2, 17, 23, 48, 17, 984000, tzinfo=UTC)
 datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
 datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
 datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
 ...
 datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
 datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
 ...
 datetime.datetime(2011, 2, 17, 23, 48, 18, 15000, tzinfo=UTC)
 datetime.datetime(2011, 2, 17, 23, 48, 18, 15000, tzinfo=UTC)
 datetime.datetime(2011, 2, 17, 23, 48, 18, 15000, tzinfo=UTC)
 datetime.datetime(2011, 2, 17, 23, 48, 18, 125000, tzinfo=UTC)
 Traceback (most recent call last):
   File stdin, line 2, in module
   File
 C:\Python27\lib\site-packages\pytz-2011b-py2.7.egg\pytz\__init__.py, li
 ne 186, in utcoffset
 KeyboardInterrupt


 Simon

 On Thu, Feb 17, 2011 at 4:58 PM, Tres Seaver tsea...@palladion.com wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 02/17/2011 06:58 AM, Zope Tests Summarizer wrote:

 Subject: FAILED : Zope Buildbot / zopetoolkit-1.1_win-py2.5 slave-win
 From: jdriessen at thehealthagency.com
 Date: Wed Feb 16 15:03:12 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032218.html

 Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.5 slave-win
 From: jdriessen at thehealthagency.com
 Date: Wed Feb 16 15:18:08 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032223.html

 Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.6 slave-win
 From: jdriessen at thehealthagency.com
 Date: Wed Feb 16 15:25:31 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032226.html

 These three failures are due to a quirk in how datetime.datetime repr
 works:  if the 'microseconds' field happens to be zero, it isn't
 printed, e.g.:

 Expected:
datetime.datetime(DATETIME, tzinfo=UTC)
 Got:
datetime.datetime(2011, 2, 16, 20, 0, 43, tzinfo=UTC)

 The regex (in zope.dublincore.tests.test_timeannotators), expects the
 microseconds value to be present:

  datetime_re = (
 '[0-9]{4}, [0-9]{1,2}, [0-9]{1,2}, [0-9]{1,2}, [0-9]{1,2}, \
 [0-9]{1,2}, '
'[0-9]{1,6}')


 I have no idea why that value is suddenly exactly zero for the THA box.


 Tres.
 
 Simon,
 
 Thank you for looking into this. I am kind of happy that the error can
 be reproduced on a different windows machine.
 
 Tres,
 
 It is indeed 'special' that this error occurs only now. The windows
 builds for zope.dublincore trunk have not shown this error:
 
 http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_3%20slave-win
 http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_5%20slave-win
 http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_trunk%20slave-win
 
 How to proceed? Make the regex in
 zope.dublincore.tests.test_timeannotators less strict?
 
 I am not a pypi owner of zope.dublincore, so Tres, could you do the honors?

I made a stab at fixing the regex.  If the dev checkouts start
passing, then we can do a release.


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

iEYEARECAAYFAk1e6PsACgkQ+gerLs4ltQ4ovgCeKYvKv+DfKGtkBB4aTiaXbBe4
Ec0AoMDWuEXSZ9ZwzQJrQH5gMQtemC5n
=1xra
-END PGP SIGNATURE-

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 72 OK, 15 Failed

2011-02-17 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/17/2011 06:58 AM, Zope Tests Summarizer wrote:

 Subject: FAILED : Zope Buildbot / zopetoolkit-1.1_win-py2.5 slave-win
 From: jdriessen at thehealthagency.com
 Date: Wed Feb 16 15:03:12 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032218.html
 
 Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.5 slave-win
 From: jdriessen at thehealthagency.com
 Date: Wed Feb 16 15:18:08 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032223.html
 
 Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.6 slave-win
 From: jdriessen at thehealthagency.com
 Date: Wed Feb 16 15:25:31 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032226.html

These three failures are due to a quirk in how datetime.datetime repr
works:  if the 'microseconds' field happens to be zero, it isn't
printed, e.g.:

Expected:
datetime.datetime(DATETIME, tzinfo=UTC)
Got:
datetime.datetime(2011, 2, 16, 20, 0, 43, tzinfo=UTC)

The regex (in zope.dublincore.tests.test_timeannotators), expects the
microseconds value to be present:

 datetime_re = (
 '[0-9]{4}, [0-9]{1,2}, [0-9]{1,2}, [0-9]{1,2}, [0-9]{1,2}, \
 [0-9]{1,2}, '
'[0-9]{1,6}')


I have no idea why that value is suddenly exactly zero for the THA box.


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

iEYEARECAAYFAk1dRasACgkQ+gerLs4ltQ4R6ACfTV1r4oXAPee23hIDnA5GEaqQ
pX8AoJLVWCq35GWNDCxxqeDmyfezzg9U
=Lnxh
-END PGP SIGNATURE-

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 72 OK, 15 Failed

2011-02-17 Thread Simon Elbaz
Hi,
I have tried this code on Python 2.7.1 (r271:86832, Nov 27 2010, 18:30:46)
[MSC v.1500 32 bit (Intel)] on win32. It seems that it is possible to have
no milliseconds returned by datetime.now.

 while 1:
... datetime.now(pytz.utc)
datetime.datetime(2011, 2, 17, 23, 48, 17, 984000, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 17, 984000, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
...
datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
...
datetime.datetime(2011, 2, 17, 23, 48, 18, 15000, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, 15000, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, 15000, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, 125000, tzinfo=UTC)
Traceback (most recent call last):
  File stdin, line 2, in module
  File
C:\Python27\lib\site-packages\pytz-2011b-py2.7.egg\pytz\__init__.py, li
ne 186, in utcoffset
KeyboardInterrupt


Simon

On Thu, Feb 17, 2011 at 4:58 PM, Tres Seaver tsea...@palladion.com wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 02/17/2011 06:58 AM, Zope Tests Summarizer wrote:

  Subject: FAILED : Zope Buildbot / zopetoolkit-1.1_win-py2.5 slave-win
  From: jdriessen at thehealthagency.com
  Date: Wed Feb 16 15:03:12 EST 2011
  URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032218.html
 
  Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.5 slave-win
  From: jdriessen at thehealthagency.com
  Date: Wed Feb 16 15:18:08 EST 2011
  URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032223.html
 
  Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.6 slave-win
  From: jdriessen at thehealthagency.com
  Date: Wed Feb 16 15:25:31 EST 2011
  URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032226.html

 These three failures are due to a quirk in how datetime.datetime repr
 works:  if the 'microseconds' field happens to be zero, it isn't
 printed, e.g.:

 Expected:
datetime.datetime(DATETIME, tzinfo=UTC)
 Got:
datetime.datetime(2011, 2, 16, 20, 0, 43, tzinfo=UTC)

 The regex (in zope.dublincore.tests.test_timeannotators), expects the
 microseconds value to be present:

  datetime_re = (
 '[0-9]{4}, [0-9]{1,2}, [0-9]{1,2}, [0-9]{1,2}, [0-9]{1,2}, \
 [0-9]{1,2}, '
'[0-9]{1,6}')


 I have no idea why that value is suddenly exactly zero for the THA box.


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

 iEYEARECAAYFAk1dRasACgkQ+gerLs4ltQ4R6ACfTV1r4oXAPee23hIDnA5GEaqQ
 pX8AoJLVWCq35GWNDCxxqeDmyfezzg9U
 =Lnxh
 -END PGP SIGNATURE-

 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )