Comment 2 for bug 1955729

Ah ok, I see. Effectively, the python package is not intended for direct end user consumption. If I understand correctly, it is provided solely as a dependency of other packages in the distribution, or for creating virtual environments for end users. I used to be dismissive of python virtual environments; partly because one never knew what was the right way to make them this week, and partly because of their reputation as a tool to provide specific fixed module versions to applications that would break if a newer version was installed. However, I agree that it is a valid means for resolving the inherent conflict between distribution packaging and pip, and a useful way of making python end-user friendly, short of manually downloading and installing a fully independent variant from the internet. And python3-venv is installable via apt (if I correctly understand that this is currently the recommended way of creating virtual environments).

I'd still prefer to see some explanation given whenever anything to do with pip is invoked at the system level, as the policy requires, including recommended ways to deal with it.