[issue22031] Hexadecimal id in reprs

STINNER Victor added the comment: > Changing the repr risks breaking doctests. That's why the change was only done in Python 3.5. To port your application to Python 3.5, you can modify you doctests to use "..." (ellipsis option of doctests). > That *might* be acceptable if there was some obvi

[issue22031] Hexadecimal id in reprs

Steven D'Aprano added the comment: > Many specialized reprs follow a pattern <... at {hexadecimal id}...>. > But there are few deviations: [...] > Proposed patch makes these cases to conform with other reprs. I oppose making this change. The exact format of this generic repr of instances is no

[issue22031] Hexadecimal id in reprs

Serhiy Storchaka added the comment: Thanks Victor. Applied only in default because this issue is too minor. -- assignee: -> serhiy.storchaka resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue22031] Hexadecimal id in reprs

Roundup Robot added the comment: New changeset 4cef7b0ec659 by Serhiy Storchaka in branch 'default': Issue #22031: Reprs now always use hexadecimal format with the "0x" prefix http://hg.python.org/cpython/rev/4cef7b0ec659 -- nosy: +python-dev ___ Pyth

[issue22031] Hexadecimal id in reprs

STINNER Victor added the comment: The patch looks good to me. -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue22031] Hexadecimal id in reprs

New submission from Serhiy Storchaka: Default repr of an instance looks as: >>> object() Many specialized reprs follow a pattern <... at {hexadecimal id}...>. But there are few deviations: 1. Reprs of WeakValueDictionary and WeakKeyDictionary in the weakref module output decimal id. 2. rep