Am 29.07.2011 um 16:06 schrieb Sebastien Douche:
On Mon, Dec 13, 2010 at 14:00, Michael Howitz m...@gocept.com wrote:
Hi
I have a test section in buildout (version 1.5.2) which uses the environment
option to get os.environ configs into the test script.
But the environment configuration
On Sat, Jul 30, 2011 at 10:31, Michael Howitz m...@gocept.com wrote:
Any news on this bug?
Sadly no. Not even a bugtracker. (Nag Gary Poster about it [1].)
Sadly is the right term.
I personally use collective.xmltestreport [2] version 1.2.1 which is a fork
of zc.recipe.testrunner to
On Mon, Dec 13, 2010 at 14:00, Michael Howitz m...@gocept.com wrote:
Hi
I have a test section in buildout (version 1.5.2) which uses the environment
option to get os.environ configs into the test script.
But the environment configuration does not show up in the generated script.
The recipe
Hi,
I have a test section in buildout (version 1.5.2) which uses the environment
option to get os.environ configs into the test script.
But the environment configuration does not show up in the generated script.
The recipe I use is zc.recipe.testrunner 1.4.0 and Python 2.5 (virtualenv).
When
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/13/2010 08:00 AM, Michael Howitz wrote:
P.S.: The Bugtracker of this project
https://bugs.launchpad.net/zc.recipe.testrunner is currently
disabled, so I was unable to put this there.
Gary Poster looks to be the person to bug about that
On Dec 13, 2010, at 8:00 AM, Michael Howitz wrote:
Hi,
I have a test section in buildout (version 1.5.2) which uses the environment
option to get os.environ configs into the test script.
But the environment configuration does not show up in the generated script.
The recipe I use is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/13/2010 09:34 AM, Gary Poster wrote:
On Dec 13, 2010, at 8:00 AM, Michael Howitz wrote:
Hi,
I have a test section in buildout (version 1.5.2) which uses the
environment option to get os.environ configs into the test script.
But the
