[TIP] Fixes for mock in Python 3

Roy Williams rwilliams at lyft.com
Fri Sep 23 10:06:49 PDT 2016

Hi all,

I am investigating a migration to Python 3, and to facilitate this we are
using the -3 flag as decribed here: https://docs.python.org/3/
howto/pyporting.html#prevent-compatibility-regressions . When using this
flag I encountered some issues inside of mock itself.

Python 3 now requires you to implement `__hash__` if you implement
`__eq__`. See https://docs.python.org/3.6/reference/datamodel.html#
object.%5F%5Fhash%5F%5F .

{mock.ANY}  # Fine in Python 2, Throws in Python 3

We need to explicitly sets the `__hash__` method on these objects as `None`
to ensure the behavior is consistent in Python 3 as well as Python 2.

I've put up a PR to fix this at https://github.com/testing-
cabal/mock/pull/378 , but I am unsure if this is the correct source of
truth for Mock.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20160923/9c747cc1/attachment.html>

More information about the testing-in-python mailing list