# PEP 737 – Unify type name formatting **URL:** \ **Category:** PEPs\ **Created:** [November 29, 2023, 1:00pm UTC](https://discuss.python.org/t/pep-737-unify-type-name-formatting/39872 "2023-11-29T13:00:27Z")\ **Posts on this page:** 1\ **Showing post:** 43
**Author:** ![vstinner](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/vstinner/32/15130_2.png) [@vstinner](https://discuss.python.org/u/vstinner)\ **Post date:** [January 11, 2024, 1:58pm UTC](https://discuss.python.org/t/pep-737-unify-type-name-formatting/39872/43 "2024-01-11T13:58:10Z")
> [@vstinner](#): > > Many people asked for it in the discussions so far. I tried to find references. 2018: - Serhiy Storchaka: “I think we need to handle only two cases: short and fully qualified names. (…)” [message](https://github.com/python/cpython/issues/78776#issuecomment-1093798454) - MRAB: “%T for short form, %#T for fully qualified name”. [email](https://mail.python.org/archives/list/python-dev@python.org/message/YAJB2QUQZAF7WV4NUBN2LOGE3ACY4YJV/) - Barry Warsaw: “%t (short) and %T (long) do seem like the logical choices” [email](https://mail.python.org/archives/list/python-dev@python.org/message/XXD77YTDZ23NMJC3D2RWAGMWBXWJ66H6/) 2023: - Serhiy: “If add a specialized format, we should provide options for all reasonable variants: (…)” [message](https://github.com/python/cpython/issues/111696#issuecomment-1792916948) - Serhiy: “For different kinds of names we can use the “size” modifier.” [message](https://discuss.python.org/t/enhance-type-name-formatting-when-raising-an-exception-add-t-format-in-c-and-add-type-fullyqualname/38129/2) - Petr Viktorin: “There’s also ` __module__ + ':' + __qualname__ `, separated by semicolon rather than a dot.” [message](https://discuss.python.org/t/enhance-type-name-formatting-when-raising-an-exception-add-t-format-in-c-and-add-type-fullyqualname/38129/3) --- _[View the full topic](https://discuss.python.org/t/pep-737-unify-type-name-formatting/39872)._