[Zope-dev] AW: SVN: zope.app.container/trunk/CHANGES.txt Added release note

Hi Philipp Betreff: Re: SVN: zope.app.container/trunk/CHANGES.txt Added release note [...] I think this it can be released now. The fix you applied was needed either way, if I'm correct. GroupFolder's __init__ was not calling its own super's __init__ but the super __init__ of

[Zope-dev] Zope Tests: 5 OK

Summary of messages to the zope-tests list. Period Tue Jul 8 11:00:00 2008 UTC to Wed Jul 9 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Tue Jul 8 21:09:04 EDT 2008 URL:

[Zope-dev] Dangerous shutdown procedure behaviour

Hi. I think I discovered a dangerous code behaviour at zope shutdown. I've had a strange problem on a site where persistent objects are created from data inserted in an SQL table. Upon object creation, SQL table is updated to mark the line as imported. Such import got triggered just before a

[Zope-dev] zope.testing releases on PyPI

Hi, the zope.testing releases on PyPI are apparently a bit weird. - zope.testing 3.5.1 has been the latest released version on PyPI last week - I created V 3.5.2 on Sunday. Phillip granted me access to the zope.testing package on PyPI in order to upload 3.5.2 (which worked) - I created V

[Zope-dev] transaction.doom() and ZPublisher

Hi, I noticed that Zope 2.11 includes a recent version of the transaction module including the transaction.doom() method. But I don't see any check for it in ZPublisher. So, if any code calls transaction.doom(), the publisher will raise a user-visible exception when it tries to call commit().