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

Make the resolution order of all fields consistent. #92

Merged
merged 1 commit into from
Mar 21, 2020
Merged

Conversation

jamadden
Copy link
Member

And test this. Fixes #80.

Add Python 3.8, drop Python 3.4.

Copy link
Member

@mgedmin mgedmin left a comment

Choose a reason for hiding this comment

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

LGTMish

.travis.yml Show resolved Hide resolved
CHANGES.rst Outdated Show resolved Hide resolved
src/zope/schema/_field.py Outdated Show resolved Hide resolved
src/zope/schema/tests/test_accessors.py Show resolved Hide resolved
And test this. Fixes #80.

Add Python 3.8, drop Python 3.4.
classImplementsFirst(Object, IObject)


class implementer_if_needed(object):
Copy link
Member Author

Choose a reason for hiding this comment

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

This is probably helpful enough that it belongs in zope.interface.

@jamadden jamadden merged commit ae99e58 into master Mar 21, 2020
@jamadden jamadden deleted the issue80 branch March 21, 2020 10:28
@mgedmin
Copy link
Member

mgedmin commented Mar 21, 2020

Just as a reminder, a forced push means I cannot review the changes you've made after my first review; I'm forced to look at the entire diff again.

I don't have the energy for that right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Borked interface resolution order for boolean field
2 participants