SecurityInfo Conflicting security declarations no longer include traceback

[ChrisW]

And without the traceback, it's pretty hard to see what's causing the problem :-(

[Casey Duncan (caseman)]

I'm not sure what the behavior was like before, but the reason why there is no traceback is because there is no exception. Warnings are issued in the log containing both the class name and conflicting method or role names.

IMO, Zope should raise a hard exception and refuse to start in debug mode if there are security conflicts. I tried to implement this, but unfortunately, the code executed too early to import DevelopmentMode from Globals. It causes a circular import when ZConfig tries to load the zope.conf and everything falls over.

If someone has any insights on how I can access the debug-mode config setting inside of AccessControl.SecurityInfo, I will be happy to implement a fix for this.

[ChrisW (chris-simplistix)]

Indeed. Warnings seem particularly useless for, well, warning ;-)

I know the same frustration has bugged me for years about the SearchIndex stuff. I see the warning pop up but have no idea where it's coming from so just have to ignore it.

Is there a python bug open for this anywhere?

[Colin Watson (cjwatson)]

The zope2 project on Launchpad has been archived at the request of the Zope developers (see https://answers.launchpad.net/launchpad/+question/683589 and https://answers.launchpad.net/launchpad/+question/685285). If this bug is still relevant, please refile it at https://github.com/zopefoundation/zope2.