26 Nov
2010
26 Nov
'10
9:49 a.m.
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... regards, jw