New submission from Alexander Böhn <fish2...@gmail.com>: When creating a new type with `typing.NewType(…)` the result is a function defined on-the-fly with no reasonable `__repr__` definition – the string representation of the type looks something like e.g. “<function NewType.<locals>.new_type at 0x108ae6950>” which isn’t very useful or aesthetically appealing.
---------- components: Extension Modules messages: 327558 nosy: fish2000 priority: normal severity: normal status: open title: String representation for types created with typing.NewType(…) are opaque and unappealing type: behavior versions: Python 3.7 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue34963> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
