3 ms·
I think there is an increasing trend for developers to get confused between their tools and their output. These are your tools: * pip * pip-tools
by globular-toast 5y ago
I think there is an increasing trend for developers to get confused between their tools and their output.
These are your tools:
* pip
* pip-tools
* pipenv
* poetry
* virtualenv
* venv
* setuptools
* pyenv
* requirements.txt
* etc.
These are your outputs:
* wheel (binary),
* tarball (source).
The tools in use are completely irrelevant and only add noise to the discussions around packaging. So what actually is the problem here? Are projects delivering broken outputs (ie. bad packages)? Are they not delivering outputs at all? Those are real problems but pointing at the number of tools that exist is not helping.
- pxc 5y agoPython itself confuses sources and outputs in that not every package has consumable source tarballs— for some packages the only way to get static metadata on dependencies is by starting a build as if to get a binary output. Native dependencies are not really handled except in an ad-hoc way, either. If you want to import Python packages into a real packaging system, you are confronted with the tools whether you want to be or not.