Tres Seaver said:
Thanks for taking this initiative, Brad!
Thanks for the encouragement.
Kader got started on this and he came up with a couple of questions:
* The tests for SQLALchemy DA make use of ZopeTestCase. Is that
deprecated? I found a discussion of Zope test runners in zope-dev,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brad Allen wrote:
Tres Seaver said:
Thanks for taking this initiative, Brad!
Thanks for the encouragement.
Kader got started on this and he came up with a couple of questions:
* The tests for SQLALchemy DA make use of ZopeTestCase. Is that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brad Allen wrote:
* The tests were written for SQLALchemy 0.4, which had a
session.save method. SQLAlchemy 0.5 and 0.6 use session.add. Do we
need to maintain support for SQLAlchemy 0.4? I am tempted to make this
new release support only 0.5
Hi everyone,
another weekly meeting is coming up today and I hope see you again
around 3pm UTC at #zope at freenode. (That's a bit less than 4 hours
from now on.)
Last week's summary is here:
https://mail.zope.org/pipermail/zope-dev/attachments/20100421/b1da5f70/attachment-0001.
Agenda
Summary of messages to the zope-tests list.
Period Mon Apr 26 12:00:00 2010 UTC to Tue Apr 27 12:00:00 2010 UTC.
There were 16 messages: 6 from Zope Tests, 9 from ccomb at free.fr, 1 from ct
at gocept.com.
Test failures
-
Subject: FAILED: Repository policy check found errors in 670
Hello Stephan,
I think for the short time I'll just put it back to KGS, because the win32
tests have that much failures that if I would start to fix them the KGS will
never be released. :-S
OTOH, once the win tests pass it would be great to keep them that way.
That means at least a buildbot is
Stephan Richter wrote:
On Monday 26 April 2010, Martijn Faassen wrote:
Could someone give me and Hanno pypi access to zope.browserresource and
zope.browsermenu?
I am in the process to give you access to all the packages that I am an owner
of (now that PyPI is fixed again. :-)
Let me
I've been working on zope.tetsing lately. The main impetus behind this
is Python 3 compatibility, but also general cleanup. This work was
discussed on #zope bu Jim Fulton, Stephan Richter, Charlie Clark and
me. The conclusion was to release a backwards incompatible
zope.testing 4.0.0.
The
On Tue, Apr 27, 2010 at 8:30 PM, Lennart Regebro rege...@gmail.com wrote:
I've been working on zope.tetsing lately. The main impetus behind this
is Python 3 compatibility, but also general cleanup. This work was
discussed on #zope bu Jim Fulton, Stephan Richter, Charlie Clark and
me. The
On Tue, Apr 27, 2010 at 21:49, Jonathan Lange j...@mumak.net wrote:
On Tue, Apr 27, 2010 at 8:30 PM, Lennart Regebro rege...@gmail.com wrote:
I've been working on zope.tetsing lately. The main impetus behind this
is Python 3 compatibility, but also general cleanup. This work was
discussed on
Am 17.04.2010, 03:41 Uhr, schrieb Tres Seaver tsea...@palladion.com:
The trickier testing bits we would re-write as super thorough, no
shortcuts-taken unit tests: one testcase class per class (or API
function) under test, at least one method per class-under-test method,
with more preferred
On Tue, Apr 27, 2010 at 3:30 PM, Lennart Regebro rege...@gmail.com wrote:
I've been working on zope.tetsing lately. The main impetus behind this
is Python 3 compatibility, but also general cleanup. This work was
discussed on #zope bu Jim Fulton, Stephan Richter, Charlie Clark and
me. The
Summary of messages to the cmf-tests list.
Period Mon Apr 26 12:00:00 2010 UTC to Tue Apr 27 12:00:00 2010 UTC.
There were 5 messages: 5 from CMF Tests.
Tests passed OK
---
Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.6 : Linux
From: CMF Tests
Date: Mon Apr 26 21:46:15 EDT 2010
URL:
13 matches
Mail list logo
