[docs] [issue33039] int() and math.trunc don't accept objects that only define __index__

Nick Coghlan report at bugs.python.org
Sat Mar 10 06:34:44 EST 2018

Nick Coghlan <ncoghlan at gmail.com> added the comment:

Marking this as a documentation enhancement request for now, but I think we should also consider changing the type creation behaviour in 3.8 to implicitly add __int__ and __trunc__ definitions when __index__ is defined, but they aren't.

That way, no behaviour will change for classes that explicitly define __int__ or __trunc__, but classes that only define __index__ without defining the other methods will behave more intuitively.

assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
stage:  -> needs patch
type:  -> enhancement
versions: +Python 3.6, Python 3.7, Python 3.8

Python tracker <report at bugs.python.org>

More information about the docs mailing list