On 28 Apr 2008, at 17:12 , Uli Fouquet wrote:
> No need to shout, Philipp!
Don't worry, I wasn't shouting :)
> Why do you always look into zope.app.securitypolicy? This package is
> simply not used by Grok 0.12 any more. The versions.cfg changed.
> zope.app.securitypolicy was pulled in by grok releases before 0.12
> only.
> Dependent packages fetch it only, when their testrunners are
> installed.
I see. So it appears setup.py / versions.cfg were updated but
ftesting.zcml wasn't. That explains the mysteriously missing
zope.app.securitypolicy. Your patch sounds fine then :) I was just
worried we were plastering over a problem that had its roots somewhere
completely else.
On 28 Apr 2008, at 17:12 , Uli Fouquet wrote:
> No need to shout, Philipp!
Don't worry, I wasn't shouting :)
> Why do you always look into zope.app. securitypolicy? This package is securitypolicy was pulled in by grok releases before 0.12
> simply not used by Grok 0.12 any more. The versions.cfg changed.
> zope.app.
> only.
> Dependent packages fetch it only, when their testrunners are
> installed.
I see. So it appears setup.py / versions.cfg were updated but securitypolicy. Your patch sounds fine then :) I was just
ftesting.zcml wasn't. That explains the mysteriously missing
zope.app.
worried we were plastering over a problem that had its roots somewhere
completely else.