twine | Utilities for interacting with PyPI | Build Tool library

There is no direct way of knowing which exact package causes the name conflict, but here are some tips that may help you further in your search.

First of all, you can find the source code of pypi (called warehouse) at https://github.com/pypa/warehouse/. Using the error message you gave, you can find that the failing check is caused by a database function called ultranormalize_name. Now, searching for that name in the codebase leads you to this migration script where the function seems to be created, which performs the following steps to check if the name is already reserved:

1. Both cases of o (lower and upper case, o and O) gets replaced with 0 (irrelevant for your case, as there are no os in your package name)
2. Both cases of L and I are replaced with 1 (e.g., example is same as examp1e and exampie)
3. All ., _, and - characters are removed (e.g., e-x-a-m-p-l-e is same as example)
4. The result is then lowercased and compared to the already existing names

As I cannot see a direct match for your given package name, are you sure examplepkg is the name that is also in your pyproject.toml or setup.py file metadata? If yes, there is probably some variant of that name whose non-normalized form matches to yours after the transformations mentioned above.

After a few days I was able to find the solution

Firstly, my code needed to be fixed to correctly call the params needed with the proper name

It's funny, but I had the same frustration when trying to install scripts on multiple platforms. (As Python calls them; posix and nt.)

So I wrote setup-py-script in 2020. It's up on github now.

It installs scripts that use their own modules as a self-contained zip-file. (This method was inspired by youtube-dl.) That means no more leftover files when you delete a script but forget to remove the module et cetera.

It does not require root or administrator privileges; installation is done in user-accessible directories.

You might have to structure your project slightly differently; the script itself is not in the module directory. See the project README.

I missed a dependency, qt5-default. I ended up having these lines for Mayavi running on Docker/CircleCi:

I used the following page suggested by @Gonzalo Odiard:

https://docs.python.org/3/distutils/setupscript.html#installing-package-data

First, I moved data folder to AAA folder and then I added package_dir={'AAA': 'AAA'} to setup.py and the problem was solved.

The index URL isn’t right, it needs to end with “/simple”. See here:

https://help.sonatype.com/display/NXRM3/PyPI+Repositories#PyPIRepositories-ConfiguringPyPIClientTools

You can have only one index but you can have as many extra indices as you wish. Add the main PyPI as an extra index:

It appears people put the tests/ folder inside the module directory when they want to distribute them along with the code.

Related SO question.

You can see the project structure they use here.

Edit: This link suggests that you just have to list the directories in your setup.py

You only need to include the src folder, .gitinore, LICENSE, README.md, and setup.py. Ideally you always want to re-build before publishing to Pypi, so you do not need the dist folder.

However, I recommend using the dependency management tool poetry, which uses a pyproject.toml instead of the setup.py. It's much more human-readable and easier to manage than the old-fashioned setup.py.

poetry also allows publishing your package to Pypi with a single command poetry publish --build ....