Stephan Richter wrote:
On Friday 01 February 2008, Chris Withers wrote:
Stephan Richter wrote:
If you use buildout, there is a recipe for creating a test runner. See
http://svn.zope.org/zope.kgs/trunk/?rev=83325
for a good example.
Where's the actual test runner or test runner creater?
On Friday 01 February 2008, Chris Withers wrote:
Stephan Richter wrote:
If you use buildout, there is a recipe for creating a test runner. See
http://svn.zope.org/zope.kgs/trunk/?rev=83325
for a good example.
Where's the actual test runner or test runner creater?
[test]
recipe =
Stephan Richter wrote:
If you use buildout, there is a recipe for creating a test runner. See
http://svn.zope.org/zope.kgs/trunk/?rev=83325
for a good example.
Where's the actual test runner or test runner creater?
Also, what's the best way to indicate in setup.py that my package needs
On Wednesday 05 December 2007, Chris Withers wrote:
I've come to realise that a lot of the python packages I've developed
for use outside of zope (twiddler and mailinglogger spring to mind) rely
on zope.testing and work best with the testrunner in zope.testing.
What's the best way to use
Hi All,
I've come to realise that a lot of the python packages I've developed
for use outside of zope (twiddler and mailinglogger spring to mind) rely
on zope.testing and work best with the testrunner in zope.testing.
What's the best way to use this in a non-zope environment?
Also, what's
