Comment 5 for bug 223247

Philipp von Weitershausen:
> Quoting Uli Fouquet <email address hidden>:
> > Philipp von Weiterhausen wrote:
> >
> >> Shouldn't zope.app.securitypolicy have backward-compatibility imports?
> >
> > Holy sh..., you're right. Apparently the backwards compatibility should
> > work but does not. I was not aware of this and will investigate. Can you
> > name a package where such a backwards compatibility works? Just for
> > comparison and to learn.
>
> There are numerous packages in Zope that provide BBB imports. It's
> usually just a matter of importing the object that was moved. I've
> just verified that zope.app.securitypolicy actually *has* BBB imports
> (it goes a bit further by using zope.deferredimport.deprecated). So,
> as I've said in my earlier message (which you're not quoting), it
> seems that zope.app.securitypolicy isn't actually pulled in. THIS is
> what should be investigated. Quoting my previous message:
>
> """
> Judging from the original error,
>
> ImportError: Couldn't import zope.app.securitypolicy.zopepolicy,
> No module named securitypolicy.zopepolicy,
>
> it seems that zope.app.securitypolicy isn't even available. The
> reasons for this should first be investigated, I suspect something
> else is at fault here.
> """

No need to shout, Philipp!

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.