# Python API exposure mechanisms (public/internal) - determining status quo

**URL:** <https://discuss.python.org/t/python-api-exposure-mechanisms-public-internal-determining-status-quo/108869>\
**Category:** Ideas\
**Created:** [September 3, 2026, 1:54am UTC](https://discuss.python.org/t/python-api-exposure-mechanisms-public-internal-determining-status-quo/108869 "2026-09-03T01:54:46Z")\
**Posts on this page:** 1\
**Showing post:** 40

<div class="post-metadata">

**Author:** ![pf\_moore](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/pf_moore/32/35_2.png) [@pf\_moore](https://discuss.python.org/u/pf_moore)\
**Post date:** [September 14, 2026, 6:52pm UTC](https://discuss.python.org/t/python-api-exposure-mechanisms-public-internal-determining-status-quo/108869/40 "2026-09-14T18:52:50Z")

</div>

> [@barry](#):
>
> It’s not outside the realm of possibility that `dir()` could grow a keyword-only argument that would enable more specific meaning to “interesting”, e.g. `dir(public=True)` or some such.

Absolutely. As I said, that’s a topic for a different thread, not for this one, though.

---

_[View the full topic](https://discuss.python.org/t/python-api-exposure-mechanisms-public-internal-determining-status-quo/108869)._