# A two-namespace model for Python modules to distinguish public/internal

**URL:** <https://discuss.python.org/t/a-two-namespace-model-for-python-modules-to-distinguish-public-internal/108593>\
**Category:** Ideas\
**Created:** [August 16, 2026, 5:21pm UTC](https://discuss.python.org/t/a-two-namespace-model-for-python-modules-to-distinguish-public-internal/108593 "2026-08-16T17:21:26Z")\
**Posts on this page:** 1\
**Showing post:** 56

<div class="post-metadata">

**Author:** ![timhoffm](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/timhoffm/32/19468_2.png) [@timhoffm](https://discuss.python.org/u/timhoffm)\
**Post date:** [August 23, 2026, 10:10am UTC](https://discuss.python.org/t/a-two-namespace-model-for-python-modules-to-distinguish-public-internal/108593/56 "2026-08-23T10:10:20Z")

</div>

**Poll: Public/internal handling — what behavior do we want?**

The recent discussions show that there are several different expectations for how public and internal should work. I’ve created a poll to collect a broader view of these preferences before we settle on a particular approach.

Please take a moment to vote here: [Poll: Public/internal handling — what behavior do we want?](https://discuss.python.org/t/poll-public-internal-handling-what-behavior-do-we-want/108706)

---

_[View the full topic](https://discuss.python.org/t/a-two-namespace-model-for-python-modules-to-distinguish-public-internal/108593)._