This is a somewhat controversial topic, and the answer for the moment is that there is no one single tool that everyone agrees is the “right way” to build source distributions, nor what that tool would be. You can see a long thread about it on the Python Packaging discourse. I hesitate to give too … Read more
As per PyPi documentation: There are four different packages (see options 1, 2, 3 and 4 below): Packages for standard desktop environments: Option 1 – Main modules package: pip install opencv-python Option 2 – Full package (contains both main modules and contrib/extra modules): pip install opencv-contrib-python (check contrib/extra modules listing from OpenCV documentation) Packages for … Read more
it looks like you didnt specify your host like the doc of simplepy said you need to setup your ~/.pypirc with the good hostname like To use it run “simplepypi”. You can upload packages by: […] Not using twine yet? Here is the legacy way of uploading Python packages (not recommended): Modify your ~/.pypirc so … Read more
The tar.gz file is a source archive whereas the .whl file is a built distribution. Newer pip versions preferentially install built distributions, but will fall back to source archives if needed. You should always upload a source archive and provide built archives for the platforms your project is compatible with. In this case, our example … Read more
There are at least two packages that help with this: pypstats and vanity. Vanity is very easy to use from the command line: vanity numpy and you’ll get a printout to your console.
To answer your 1st point let me rephrase my answer to a different question. The biggest source of misunderstanding is that the word “package” is heavily overloaded. There are 4 different names in the game — the name of the repository, the name of the directory being used for development (the one that contains setup.py), … Read more
It might not be the solution for you, but I tell what we do. Prefix the package names, and using namespaces (eg. company.product.tool). When we install our packages (including their in-house dependencies), we use a requirements.txt file including our PyPI URL. We run everything in container(s) and we install all public dependencies in them when … Read more
You need to register it first. python setup.py register Then you can python setup.py sdist upload
Late to the party, but never hurts to help fellow travellers down the namespace path in Python! #1: With the __init__.py, which of these should I be using (if any)?: It depends, There are three ways to do namespace packages as listed here: Use native namespace packages. This type of namespace package is defined in … Read more
The easiest way to do this is to use the simple index at PyPI which lists all packages without overhead. You can then request the JSON of each package individually by performing a GET request to the URLs mentioned in your question.