[issue24391] Better repr for threading objects

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

I agree, that the address is the least interesting thing, and I think this is an argument to make it the last thing in the repr (at least for those of us who read from left to right). Many objects in different modules outputs the address last. The only exceptions are asyncio (just because it constructs reprs from super().__repr__(), including verbose "object" after type name), concurrent.futures and weakref.finalize (the latter contains multiple addresses in any case). Do we need "object" after type name?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue24391>
_______________________________________