Description
Hi,
At the moment, lit is available on Pypi as a 'source distribution'/'sdist' i.e. a tarball source (here), but not as a 'built distribution'/'bdist' (normally a 'wheel').
It is recommended to upload built versions as well, e.g. from the python packaging tutorial:
You should always upload a source distribution and provide built distributions for the platforms your project is compatible with.
This is potentially as simple as changing this line
from:
python3 setup.py sdistto:
python3 setup.py sdist bdist_wheel(although I don't know lit well so it could be more complicated if the codebase is much more complex than just pure python).
This is particularly a problem in my case, using a http proxy in a corporate environment. In this case, I actually have to 'build' the wheel myself on my laptop and copy it over into the relevant environment, and specify a dependency on that built wheel. So the lack of a wheel causes considerable pain for me here.
Full details of http proxy issues with pip installs of sdist-only packages
Pip will 'build' dependencies like lit that only provide an 'sdist' in an 'isolated environment' now, which means downloading and installing their declared build dependencies (setuptools in lit's case). Unfortunately, that 'isolated environment' does not include http proxies: see this issue for pip pypa/pip#6018. This means that setuptools cannot be downloaded, so the whole install fails.
Some more benefits of uploading wheels, from https://pythonwheels.com:
Advantages of wheels
Faster installation for pure Python and native C extension packages.
Avoids arbitrary code execution for installation. (Avoids setup.py)
Installation of a C extension does not require a compiler on Linux, Windows or macOS.
Allows better caching for testing and continuous integration.
Creates .pyc files as part of installation to ensure they match the Python interpreter used.
More consistent installs across platforms and machines.