-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OFS.ObjectManager.__contains__ optimisation conflicts with catalog #69
Comments
Looks like That function overwrites objectIds and doesn't look into _objects, but a different place. The PR takes away the objectIds indirection and thus breaks this kind of use-case. I'd be inclined to revert the PR on the 2.13 branch. For Zope 4 we can leave it in and extend the subclass contract by demanding subclasses also overwrite |
@hannosch SGTM |
Inheritance in OOP is just wrong :-) |
The optimization is undone on the 2.13 branch. For 4.0 I've updated the ZCatalogIndexes class to also implement |
Grepping through Plone 5.0 I see the following that are affected, so having
@thet Is that maybe solved already in your branches for getting Plone to run on Zope 4? |
I am trying this on the Plone 5.0 development buildout. It is using Zope2 2.13.24. Instead I checked out Zope2 branch 2.13 and this resulted in a few failures on our Jenkins test server: http://jenkins.plone.org/job/plone-5.0-python-2.7/4932/
I focused on the plone.app.folder one:
http://jenkins.plone.org/job/plone-5.0-python-2.7/4932/testReport/junit/plone.app.folder.tests.test_integration/FolderReplacementTests/testGetObjPositionInParentIndex/
That can be seen in a debug session too:
With Zope2 tag 2.13.24 this error goes away.
The breaking point is with the merge of pull request #62.
The text was updated successfully, but these errors were encountered: