Summary of messages to the zope-tests list.
Period Mon Dec 22 12:00:00 2008 UTC to Tue Dec 23 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Mon Dec 22 20:36:40 EST
Hi Tim
I'm more involved with Plone but can provide a slightly more
digestible answer :)
Chris mentioned unit tests. You do not have to write a new unit test.
What is required is to have a look at the tests and then identify one
that is relevant to your problematic method. This test should be
Hi Thomas. Very cool that you are working on zc.dict + zc.blist.
The updateOrder API is a sucky API for blists, as I'm sure you've
realized. :-)
FWIW, I seem to recall that Plone has a reasonable-to-nice API for
changing order in containers, and the API would be able to take much
better
Gary Poster gary.pos...@gmail.com schrieb:
Hi Thomas. Very cool that you are working on zc.dict + zc.blist.
Better than letting that branch get old ;o)
The updateOrder API is a sucky API for blists, as I'm sure you've
realized. :-)
It is sucky even when used with a PersistentList; it's
Thomas Lotze t...@gocept.com schrieb:
Yes, and I think that we're talking about two steps here anyway. I'd
like to finish and release a version that uses BLists ASAP;
Well, I think the switch to BLists is finished, so I'd be ready to
merge it to the trunk after someone reviewed the changes. In
On Dec 23, 2008, at 2:11 PM, Thomas Lotze wrote:
Thomas Lotze t...@gocept.com schrieb:
Yes, and I think that we're talking about two steps here anyway. I'd
like to finish and release a version that uses BLists ASAP;
Well, I think the switch to BLists is finished, so I'd be ready to
merge
Gary Poster gary.pos...@gmail.com schrieb:
OK. I'll give it a whirl sometime over the next couple of weeks, if
that's soon enough for you.
Sure.
FWIW, I'd be strongly tempted to release *without* the generation
code, and leave it up to users to switch as they desire.
Fine with me. I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marius Gedminas wrote:
On Fri, Dec 12, 2008 at 12:45:27PM +, Malthe Borch wrote:
Martijn Pieters wrote:
The C extension is required to make messageids immutable. Because they
are immutable, the security machinery can treat them as rocks, e.g.
