-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/26/2010 04:49 AM, Jan-Wijbrand Kolman wrote:
On 11/26/10 8:37 AM, Michael Howitz wrote:
currently the ZTK tests on the trunk do not run successfully in a virtualenv. <sip> But reverting this change does not help to get the tests of z3c.recipe.compattest itself running again. There are the same errors like before.
Is it intensional that ZTK tests fail in virtualenv? What needs be done to get the tests running again in virtualenv?
I don't think this was intentional. Then again, I guess it __was__ the intention to make use of the system-python-path-isolation-features in zc.buildout. Personally, I'm not sure where to start fixing this, help and insights appreciated...
I'd rather shoot the system-python-with-isolation features in the head, myself. Anybody *developing* ZTK should be willing and able to set up either an alternative Python installation or a virtualenv. FWIW, I'm not using zc.buildout >= 1.5.0devel anywhere because of the breakage it induces in my normal workflow. 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/ iEYEARECAAYFAkzv14MACgkQ+gerLs4ltQ7KmACeMi+Dza/VQ0J3d5vi77Dahp4I LYYAoK9nP1WlERGGq4dSRllS40QD9Hiv =RIRM -----END PGP SIGNATURE-----