# "too similar" error with namespace project

**URL:** <https://discuss.python.org/t/too-similar-error-with-namespace-project/25552>\
**Category:** Packaging\
**Tags:** release\
**Created:** [April 7, 2023, 12:07pm UTC](https://discuss.python.org/t/too-similar-error-with-namespace-project/25552 "2023-04-07T12:07:26Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Debith](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/debith/32/11937_2.png) [@Debith](https://discuss.python.org/u/Debith)\
**Post date:** [April 7, 2023, 12:07pm UTC](https://discuss.python.org/t/too-similar-error-with-namespace-project/25552/1 "2023-04-07T12:07:26Z")

</div>

I am developing a library and want to release it on PyPI. It worked fine when I published part of the project under the name ‘pygim-common,’ but when I tried to release the ‘master’ project as ‘pygim,’ it failed because the names are too similar.

Background:  
I intend to use ‘pygim’ as the entry point for all other projects and ‘pygim-common’ as the main shared package with all other namespace projects. I understand that ‘pygim’ and ‘pygim-common’ have some similarities in their names, but how do I deal with this? I want it to be possible to install the main project by running ‘pip install pygim,’ which installs the common package at the same time, as well as the associated command-line interface later on.

Any ideas how to solve this?

---

<div class="post-metadata">

**Author:** ![ronaldoussoren](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ronaldoussoren/32/61_2.png) [@ronaldoussoren](https://discuss.python.org/u/ronaldoussoren)\
**Post date:** [April 7, 2023, 12:33pm UTC](https://discuss.python.org/t/too-similar-error-with-namespace-project/25552/2 "2023-04-07T12:33:53Z")

</div>

It’s probably too similar to [pygmy](https://pypi.org/project/pygmy/), the names “pygim” en “pygmy” are close enough that I’d expect the typo-squatting protection kicks in.

---

<div class="post-metadata">

**Author:** ![Debith](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/debith/32/11937_2.png) [@Debith](https://discuss.python.org/u/Debith)\
**Post date:** [April 7, 2023, 1:29pm UTC](https://discuss.python.org/t/too-similar-error-with-namespace-project/25552/3 "2023-04-07T13:29:06Z")

</div>

Thanks for your response! Is there a way to be sure? Twine doesn’t seem to give any details on this.

---

<div class="post-metadata">

**Author:** ![njs](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/njs/32/204_2.png) [@njs](https://discuss.python.org/u/njs)\
**Post date:** [April 7, 2023, 6:46pm UTC](https://discuss.python.org/t/too-similar-error-with-namespace-project/25552/4 "2023-04-07T18:46:14Z")

</div>

Unfortunately the exact details of the typo-squatting protection aren’t public, because if they were then typo-squatters would immediately exploit them to find any gaps.

---

<div class="post-metadata">

**Author:** ![dustin](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/dustin/32/149_2.png) [@dustin](https://discuss.python.org/u/dustin)\
**Post date:** [April 7, 2023, 7:04pm UTC](https://discuss.python.org/t/too-similar-error-with-namespace-project/25552/5 "2023-04-07T19:04:43Z")

</div>

> [@njs](#):
>
> Unfortunately the exact details of the typo-squatting protection aren’t public, because if they were then typo-squatters would immediately exploit them to find any gaps.

It’s pretty public: we use [this function](https://github.com/pypi/warehouse/blob/8615326918a180eb2652753743eac8e74f96a90b/warehouse/migrations/versions/d18d443f89f0_ultranormalize_name_function.py#L29-L42).

> [@ronaldoussoren](#):
>
> It’s probably too similar to [pygmy](https://pypi.org/project/pygmy/), the names “pygim” en “pygmy” are close enough that I’d expect the typo-squatting protection kicks in.

The issue here is that `pygim` conflicts with [http://pypi.org/p/pyglm](http://pypi.org/p/pyglm).

> [@Debith](#):
>
> Any ideas how to solve this?

File an issue [here](https://github.com/pypi/support/issues/new?assignees=&labels=PEP+541&template=pep541-request.yml&title=PEP+541+Request%3A+PROJECT_NAME) and we’ll very likely be able to release this for you.

---

<div class="post-metadata">

**Author:** ![njs](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/njs/32/204_2.png) [@njs](https://discuss.python.org/u/njs)\
**Post date:** [April 7, 2023, 7:18pm UTC](https://discuss.python.org/t/too-similar-error-with-namespace-project/25552/6 "2023-04-07T19:18:58Z")

</div>

> [@dustin](#):
>
> It’s pretty public: we use [this function](https://github.com/pypi/warehouse/blob/8615326918a180eb2652753743eac8e74f96a90b/warehouse/migrations/versions/d18d443f89f0_ultranormalize_name_function.py#L29-L42).

oh nice, thanks for the correction!

---

<div class="post-metadata">

**Author:** ![Debith](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/debith/32/11937_2.png) [@Debith](https://discuss.python.org/u/Debith)\
**Post date:** [April 8, 2023, 8:15am UTC](https://discuss.python.org/t/too-similar-error-with-namespace-project/25552/7 "2023-04-08T08:15:46Z")

</div>

> File an issue [here](https://github.com/pypi/support/issues/new?assignees=&labels=PEP+541&template=pep541-request.yml&title=PEP+541+Request%3A+PROJECT_NAME)and we’ll very likely be able to release this for you.

Thanks for your help!
