zopefoundation / zope.schema

100%

master: 100%

LAST BUILD ON BRANCH issue36

branch: issue36

CHANGE BRANCH

x

Reset

• issue36
• 4.5.0
• 4.6.0
• 4.6.1
• 4.6.2
• 4.7.0
• 4.8.0
• 4.9.0
• 4.9.2
• 4.9.3
• 5.0
• 5.0.1
• 6.0.0
• 6.1.1
• 6.2.0
• 6.2.1
• 7.0.0
• 7.0.1
• 7.1
• 8.0
• adamg-decimal
• adamg-fix-text
• add-python-requires
• all-repos_autofix_all-repos-sed
• changes-on-rtd
• config-with-pure-python
• config-with-pure-python-template-3ea7ef32
• config-with-pure-python-template-b21fbbf2
• dataflake/fix_115
• doc-IFromBytes
• dottedname_allow_underscore
• feature/IFromBytes
• fix-datetime-typo
• fix-lint
• fix-non-ascii-bytes-tokens
• fix_init_on_none_description
• issue10
• issue11
• issue13
• issue15
• issue16
• issue17
• issue18
• issue23
• issue35
• issue40
• issue42
• issue49
• issue60
• issue63
• issue65
• issue66
• issue69
• issue74
• issue76
• issue80
• issue86
• issue9
• jugmac00-patch-1
• master
• pep-420-native-namespace
• py36
• re36-fields-hashable
• setuptools-dep
• sphinx-8
• tseaver-drop_setup_py_test_fossils

Build # 95

Build Type

Pull #39

travis-ci

Committed by web-flow

Commit Message

``Field`` instances are hashable on Python 3

They use a defined hashing algorithm that matches what equality does
on all versions of Python. Previously, on Python 2, fields were hashed
based on their identity. This violated the rule that equal objects
should have equal hashes, and now they do. Since having equal hashes
does not imply that the objects are equal, this is not expected to be
a compatibility problem.

Included tests with a dict show that there shouldn't be false matches
even with equal hashes.

Fixes #36

Pull Request Pull Request #39: ``Field`` instances are hashable on Python 3

Run Details

30 of 30 new or added lines in 2 files covered. (100.0%)

4828 of 4828 relevant lines covered (100.0%)

4.99 hits per line