Summary of messages to the zope-tests list.
Period Sat Aug 7 12:00:00 2010 UTC to Sun Aug 8 12:00:00 2010 UTC.
There were 45 messages: 6 from Zope Tests, 13 from buildbot at winbot.zope.org,
8 from ccomb at free.fr, 5 from ct at gocept.com, 13 from jdriessen at
thehealthagency.com.
Test
Hi Jim,
On 08/08/2010, Jim Fulton j...@zope.com wrote:
On Thu, Aug 5, 2010 at 2:36 AM, Martin Aspeli optilude+li...@gmail.com
wrote:
...
I have a package (plone.registry) that currently has a persistent
structure like this:
Registry(Persistent)
|
+-- Records(Persistent)
|
On Sun, Aug 8, 2010 at 2:21 PM, Martin Aspeli optilude+li...@gmail.com wrote:
On 08/08/2010, Jim Fulton j...@zope.com wrote:
On Thu, Aug 5, 2010 at 2:36 AM, Martin Aspeli optilude+li...@gmail.com
wrote:
What is the best way to manage this type of migration?
Today, it probably makes the most
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
Log message for revision 11:
Replaced failUnless with assertTrue and failIf with assertFalse in tests.
Hmm, I don't like the way 'asseertTrue' and 'assertFalse' read -- is
there a particular rationale for this change
On Mon, Aug 9, 2010 at 12:00 AM, Tres Seaver tsea...@palladion.com wrote:
Hanno Schlichting wrote:
Log message for revision 11:
Replaced failUnless with assertTrue and failIf with assertFalse in tests.
Hmm, I don't like the way 'asseertTrue' and 'assertFalse' read -- is
there a
On 8 August 2010 20:29, Hanno Schlichting ha...@hannosch.eu wrote:
There should be some way of doing this with custom __getstate__ and
__setstate__ methods.
It's just tricky to get right and a bit fragile. It's much easier to
write the migration code if both the old and new class are