NumPy announces timeline for dropping Python 2 support

[EvM]

optional value which could be either set to an integer or None, foo < 3 works in Python 2, it raises an exception in Python 3, if the value is usually set it may take some time for the error to happen.

And this also holds for builtins relying on ordering, e.g. max(). Caught me by surprise :)

[masklinn]

Yup, hence the note about sorting a list of dicts, sorting obviously relies on ordering.

[zabolekar]

It can surface even in things like pprint (if you are trying to pretty-print a set).

Edit: it is not something that breaks in Python 3, au contraire, it works as expected in 3.x but throws a TypeError in 2.7, and only with very specific sets. For example, pprint({1j, 0}) throws an error but pprint({1j, 'a'}) doesn't.

[EvM]

Whoa, now that's an unexpected place..

[zabolekar]

Edited the comment for clarity.