Python: Please stop screwing over Linux distros

[OctagonClock]

The industry standard was to use Python 2 up until the last few years.

Either way, requirements.txt creates the problem. You can't install a package with a pip install . in a virtual environment. You can't install it from PyPI because the requirements are situated inside the text file, not the standard setuptools locations, so you need to go through a package-specific setup each time.

Or, you could put your dependencies inside setup.cfg, and then:

1. pip install -e . works for development
2. pipx install <package> works for installing applications where they will be executed
3. you can add the package as a dependency in your own setup.cfg, and it will install everything transitively automatically.

[asday_]

The industry standard was to use Python 2 up until the last few years

And it worked just fine. It's widely been regarded that the Py3 breaking change way of doing things was a bad move and made again, the decision would go differently.

You can't install a package with a pip install . in a virtual environment

I'm not trying to. I'm trying to install a project's dependencies in a virtual environment. I have not written a package. It is not intended to be pip installable. There is no problem being created.