Tim Cook wrote:
As I said before I may have miss-diagnosed the problem and may fix may
break other things?
This is what a full-coverage unit and functional test suit is for.
You have got automated tests for all this stuff, right?
Chris
--
Simplistix - Content Management, Zope Python
Summary of messages to the zope-tests list.
Period Thu Dec 18 12:00:00 2008 UTC to Fri Dec 19 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: Thu Dec 18 20:35:54 EST
Hi Guys,
Line 396 of doctest.py contains code which is, at best,
platform-specific (and so a bug) or, more likely, irrelevent.
I have the following code that runs the tests in all my package's docs:
def test_suite():
suite = unittest.TestSuite()
for path in \
On Fri, Dec 19, 2008 at 1:03 PM, Chris Withers ch...@simplistix.co.uk wrote:
Hi Guys,
Line 396 of doctest.py contains code which is, at best,
platform-specific (and so a bug) or, more likely, irrelevent.
Line 396 of doctest.py from zope.testing 3.7.1 doesn't include a raise. I'm
assuming you
Tim Cook wrote at 2008-12-18 08:35 -0200:
...
Yeah we use the really cool, robust, well tested and trusted
application server called the Zope Component Architecture because it
really shows the strengths of the open source development process. Oh,
by the way, after everything is installed you
Martijn Faassen wrote at 2008-12-18 16:27 +0100:
...
You should, and likely are, shipping your package with a recommended
list of versions.
Apparently, grok was forced to go this route.
But, in principle, this is undesirable.
Most of my components work with a wide version range of other
Hey,
On Fri, Dec 19, 2008 at 7:50 PM, Dieter Maurer die...@handshake.de wrote:
Martijn Faassen wrote at 2008-12-18 16:27 +0100:
...
You should, and likely are, shipping your package with a recommended
list of versions.
Apparently, grok was forced to go this route.
But, in principle, this is
Hi Chris,
On Fri, 2008-12-19 at 10:06 +, Chris Withers wrote:
Tim Cook wrote:
As I said before I may have miss-diagnosed the problem and may fix may
break other things?
This is what a full-coverage unit and functional test suit is for.
You have got automated tests for all this
Thanks Dieter,
On Fri, 2008-12-19 at 19:41 +0100, Dieter Maurer wrote:
I often approach situations like this with so called Monkey Patches:
I replace or enhance classes or methods during startup (triggered
by some startup event).
This may not be optimal but allows me to solve my problems
