five.localsitemanager doesn't work when explicit 'context' arguments are used in utility lookup

[Rob Miller]

Local utility lookup fails when the context argument is used to specify a lookup context that is different from the currently specified local site. Attached is a patch to localsitemanager.txt that contains failing tests that demonstrate the problem. This is using the five.localsitemanager trunk with the Zope 2.10 branch, the standard configuration for Plone 3.

I've concretely identified at least two sources of trouble:

1) Using getSiteManager(context=site) doesn't always return the right value. This is demonstrated in the test patch.

2) The five.localsitemanager.registry._wrap function makes an assumption that the registry within which the utility was found is within the acquisition chain of the current site as retrieved by getSite. This bug would be demonstrated by the test case patch, but it is currently being masked by the first issue. The fingerprint for this problem is that a getUtility call will return TypeError: ('Not enough context information to get parent' <SomeObjDefinition>) instead of either a utility or a regular component lookup error.

[Tres Seaver (tseaver)]

The attached file adds a (presumably) failing test, but does not include a fix.

[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.