# Standardized Reflection Objects for Python Callables

**URL:** <https://discuss.python.org/t/standardized-reflection-objects-for-python-callables/107563>\
**Category:** Ideas\
**Tags:** typing\
**Created:** [May 28, 2026, 2:34pm UTC](https://discuss.python.org/t/standardized-reflection-objects-for-python-callables/107563 "2026-05-28T14:34:51Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![jonathandung](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/jonathandung/32/35459_2.png) [@jonathandung](https://discuss.python.org/u/jonathandung)\
**Post date:** [August 6, 2026, 8:05am UTC](https://discuss.python.org/t/standardized-reflection-objects-for-python-callables/107563/7 "2026-08-06T08:05:34Z")

</div>

It’s not so much that the information “lives” in `inspect`. The information is in ` __code__ ` as the `co_argcount` attribute and friends, and `inspect` contains logic that makes it much more intuitively accessible.

---

_[View the full topic](https://discuss.python.org/t/standardized-reflection-objects-for-python-callables/107563)._