Summary of messages to the zope-tests list.
Period Wed Jul 29 12:00:00 2009 UTC to Thu Jul 30 12:00:00 2009 UTC.
There were 8 messages: 8 from Zope Tests.
Test failures
-
Subject: FAILED (failures=1) : Zope-2.12 Python-2.6.2 : Linux
From: Zope Tests
Date: Wed Jul 29 20:50:56 EDT
Hi,
I'm running the plone.z3cform tests in a Zope 2.10 instance with
zope.testing 3.8 installed.
All other tests seem to work OK, but with plone.z3cform's tests, I get:
$ ./bin/instance test -s plone.z3cform
Running tests at level 1
Running plone.z3cform.testing_zcml_layer tests:
Set up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
Hi.
I'd like to push code and ZCML from Products.Five into the appropriate
places in Zope2.
For example event.zcml registering events for OFS items, should live
in the OFS package. i18n.zcml setting up stuff for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Hi,
I'm running the plone.z3cform tests in a Zope 2.10 instance with
zope.testing 3.8 installed.
All other tests seem to work OK, but with plone.z3cform's tests, I get:
$ ./bin/instance test -s plone.z3cform
Running
On Thu, Jul 30, 2009 at 7:43 PM, Tres Seavertsea...@palladion.com wrote:
Hanno Schlichting wrote:
I'd like to push code and ZCML from Products.Five into the appropriate
places in Zope2.
+1 in general, as long as we don't let any zope.app dependencies leak
out while this happens.
Hhm,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
On Thu, Jul 30, 2009 at 7:43 PM, Tres Seavertsea...@palladion.com wrote:
I would also be +1 to removing the formlib and viewlet integration into
separate eggs: I don't think either of them belongs in core Zope2 at
all,
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Hi,
I'm running the plone.z3cform tests in a Zope 2.10 instance with
zope.testing 3.8 installed.
All other tests seem to work OK, but with plone.z3cform's tests, I get:
$ ./bin/instance test -s
On Thu, Jul 30, 2009 at 9:33 PM, Martin Aspelioptilude+li...@gmail.com wrote:
Unfortunately, I've got other packages that depend on a newer
zope.testing (specifically, collective.testcaselayer). But I thought
zope.testing aimed to be able to run any valid tests, so it sounds
like a bug in
