# 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:** 36

<div class="post-metadata">

### Author: ![elis.byberi](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/elis.byberi/32/35937_2.png) [@elis.byberi](https://discuss.python.org/u/elis.byberi)
#### Post date: [September 5, 2026, 8:48am UTC](https://discuss.python.org/t/python-api-exposure-mechanisms-public-internal-determining-status-quo/108869/36 "2026-09-05T08:48:43Z")

</div>

> [@edvilme](#):
>
> More specifically, if ` __all__ ` includes an underscored member, should it be public?

Explicit language semantics take precedence over conventions, though conventions may still inform the intended meaning. In this specific case, it is essentially saying, “I am intentionally exposing this underscored member.” If that happens by mistake, tests should help catch it.

---

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