[Grok-dev] Re: bug in ftesting.zcml ??
uli at gnufix.de
Mon Apr 28 12:50:38 EDT 2008
Martijn Faassen wrote:
> Philipp von Weitershausen wrote:
> > As I've pointed out in the bug tracker , I don't think ftesting.zcml
> > is at fault. Sure, it'd be nice if the template were ultimately updated
> > to the new imports, but BBB should prevail. Judging from the error
> > message, zope.app.securitypolicy isn't available in the first place,
> > which means something else is wrong.
> >  https://bugs.launchpad.net/grok/+bug/223247
> That's because it's now zope.securitypolicy, apparently. The dependency
> on zope.app.securitypolicy was changed to a dependency on
> zope.securitypolicy. This change was at fault. We should be more careful
> in changing dependencies.
So I see two ways to go from here:
1) make a new Grok release reintroducing zope.app.securitypolicy
2) update grokproject to generate ftesting.zcmls based on
If we do 1), would there be a time in future, where we could do the
switch from zope.app.securitypolicy to zope.securitypolicy whith less
hassle? Or do we only shift the problem into the future this way?
If so, then I'd opt for staying with the newer package and update
grokproject as mentioned before. What other side-effects could show up
with that change?
Or is there a third way to go?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 191 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://mail.zope.org/pipermail/grok-dev/attachments/20080428/1f7f3a80/attachment-0001.bin
More information about the Grok-dev