Skip to content
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

update zope.component and zope.interface #256

Merged
merged 1 commit into from
Nov 9, 2016
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions versions.cfg
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,8 @@ zdaemon = 4.1.0
transaction = 1.4.4
Sphinx = 1.3.6
zope.app.locales = 3.7.5
zope.component = 3.12.1
zope.interface = 4.2.0
# required for recent z3c.form and chameleon
zope.pagetemplate = 3.6.3
# Support for more complex catalog queries
Expand Down Expand Up @@ -322,3 +324,11 @@ plone.app.drafts = 1.1.1
plone.app.tiles = 2.2.1
plone.tiles = 1.8.0
plone.app.ldap = 1.4.0

[versionannotations]
# keep this alphabetical please
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Keeping it alphabetical seems very good. Can you start by moving zope.component above zope.interface? :-)
Someone can also do that manually before merging, if the pull request is good.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lol, thanks. ok, need to follow my own rules. this is just experimental.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

zope.component =
Major changes in 4.0.0, needs check if we can run Plone with them, stick with 3.12.1
zope.interface =
Starting with 4.3.0 hashing in (un-)registerUtility was changed.
This leads into "TypeError: cannot create weak reference to 'Acquisition.ImplicitAcquisitionWrapper' object".