zc.recipe.testrunner 1.4.0 no longer supports environment option?
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 running the tests of zc.recipe.testrunner with this Python many of them fail including the test for the environment option. Is it intensional that zc.recipe.testrunner does not run when using a virtualenv'ed Python? 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. Yours sincerely, -- Michael Howitz · mh@gocept.com · software developer gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development
-----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 project. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0GJAEACgkQ+gerLs4ltQ6LmACeI31OwR1XYYgEH5nXYDJ0LQ7y +PgAn2gU3a1QoHKYaez/3UtuBSgwfRT/ =cg7b -----END PGP SIGNATURE-----
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 zc.recipe.testrunner 1.4.0 and Python 2.5 (virtualenv).
When running the tests of zc.recipe.testrunner with this Python many of them fail including the test for the environment option.
Not inherently surprising nor necessarily indicative of a problem in the test suite. Some of the things that the test suite tests are not supported with virtualenv (specifically, the tests for using a system Python). That said, the underlying recipe functionality should work, so the answer to the next question is...
Is it intensional that zc.recipe.testrunner does not run when using a virtualenv'ed Python?
...no. I may get a chance to investigate this over the next few weeks, but I'm afraid I can't promise anything.
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.
I think I registered the project so I could make a branch of it in Launchpad. I'm neither the author nor the maintainer of the package. I'm happy to transfer the Launchpad project to whomever makes sense. Gary
-----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 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 running the tests of zc.recipe.testrunner with this Python many of them fail including the test for the environment option.
Not inherently surprising nor necessarily indicative of a problem in the test suite. Some of the things that the test suite tests are not supported with virtualenv (specifically, the tests for using a system Python). That said, the underlying recipe functionality should work, so the answer to the next question is...
Is it intensional that zc.recipe.testrunner does not run when using a virtualenv'ed Python?
...no.
I may get a chance to investigate this over the next few weeks, but I'm afraid I can't promise anything.
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.
I think I registered the project so I could make a branch of it in Launchpad. I'm neither the author nor the maintainer of the package. I'm happy to transfer the Launchpad project to whomever makes sense.
Maybe the zope-admin group? https://launchpad.net/~zope-admin Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0GYE4ACgkQ+gerLs4ltQ5KHgCfcJCOowneFfMo+r6tdR+yJ7Tm zzwAn13rjYezQndiyAu42mDKSM3M9vXD =UpXc -----END PGP SIGNATURE-----
On Mon, Dec 13, 2010 at 14:00, Michael Howitz <mh@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 I use is zc.recipe.testrunner 1.4.0 and Python 2.5 (virtualenv).
Any news on this bug? We're upgrading to Buildout 1.5.2 / z3c.recipe.scripts to use eggs from system site-packages, Infortunately, we use environment variables (we create a local postgresql). -- Sebastien Douche <sdouche@gmail.com> Twitter : @sdouche
Am 29.07.2011 um 16:06 schrieb Sebastien Douche:
On Mon, Dec 13, 2010 at 14:00, Michael Howitz <mh@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 I use is zc.recipe.testrunner 1.4.0 and Python 2.5 (virtualenv).
Any news on this bug?
Sadly no. Not even a bugtracker. (Nag Gary Poster about it [1].)
We're upgrading to Buildout 1.5.2 / z3c.recipe.scripts to use eggs from system site-packages, Infortunately, we use environment variables (we create a local postgresql).
I personally use collective.xmltestreport [2] version 1.2.1 which is a fork of zc.recipe.testrunner to support xml output. Although I do not need this xml feature, at least using environments works there even together with buildout 1.5.2. [1] https://bugs.launchpad.net/zc.recipe.testrunner [2] http://pypi.python.org/pypi/collective.xmltestreport Yours sincerely, -- Michael Howitz · mh@gocept.com · software developer gocept gmbh & co. kg · Forsterstraße 29 · 06112 Halle (Saale) · Germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development
On Sat, Jul 30, 2011 at 10:31, Michael Howitz <mh@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 support xml output. Although I do not need this xml feature, at least using environments works there even together with buildout 1.5.2.
Thanks for the tip Michael! -- Sebastien Douche <sdouche@gmail.com> Twitter : @sdouche
participants (4)
-
Gary Poster -
Michael Howitz -
Sebastien Douche -
Tres Seaver