# Dedicated prefix for internal, non-public packages?

**URL:** <https://discuss.python.org/t/dedicated-prefix-for-internal-non-public-packages/9866>\
**Category:** Packaging\
**Created:** [July 27, 2021, 11:01am UTC](https://discuss.python.org/t/dedicated-prefix-for-internal-non-public-packages/9866 "2021-07-27T11:01:32Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![domdfcoding](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/domdfcoding/32/2544_2.png) [@domdfcoding](https://discuss.python.org/u/domdfcoding)\
**Post date:** [July 27, 2021, 12:37pm UTC](https://discuss.python.org/t/dedicated-prefix-for-internal-non-public-packages/9866/2 "2021-07-27T12:37:08Z")

</div>

There is a (long) thread [here](https://discuss.python.org/t/namespace-support-in-pypi/1609) about namespace support on PyPI, which I think is what you’re looking for. The idea is company “foo” can reserve the `foo` prefix, so only it can upload packages like `foo.bar` to PyPI, but they’re free (and safe) to use the name internally.

---

_[View the full topic](https://discuss.python.org/t/dedicated-prefix-for-internal-non-public-packages/9866)._