unable to run pip

[Skaperen]

for those wondering about my strange output and strange commands, i have a system-wide command named logcmd that runs a command through the script command with a customized and dated log file name. then i have several commands specific to root that log things i do with packages in a unified way, such as log-pip-install and log-apt-install. try logging everything you do in a GUI environment. i am still a mostly command line user.

[Skaperen]

if there are missing dependencies, why didn't they get installed automatically or where can i get a list of all dependencies? where do distros like Debian get pip to begin with. in the C/C++ world, distros download and build source (or steal from another distro). it's the "source" for pip that i am looking fo.

[Gribouillis]

it's the "source" for pip that i am looking fo.

Here is the source code and the documentation.

[Axel_Erfurt]

I have the same error message with pip 22.1.2 (No module named 'pip._vendor.progress')

I've tried an older pip version

pip install --upgrade pip==22.0.4

and the error is gone

[Skaperen]

i had some free time today so i went through the tasks of trying the install of pip, running pip to install awscli, catching what it could not find, installing that, and repeating this whole mess. after about a dozen installs pip seems to work. but when i install awscli, it creates a directory tree at /local and puts awscli submodules in there. then awscli can't find them. but it names it as //local in error messages, suggesting to me that something should have "usr" but has "" instead. ouch! any guesses?

i would be tempted to manually wipe out all python stuff and start over, but ubuntu now depends on python, making that difficult to do.

[Gribouillis]

i would be tempted to manually wipe out all python stuff and start over,

Why not wipe out Xubuntu 20.04 and install Xubuntu 22.04 LTS ? It looks better to me.

[snippsat]

I don't why this still is problem,maybe Gribouillis advice is the easiest one.
Gave some advice in post #12

i would be tempted to manually wipe out all python stuff and start over, but ubuntu now depends on python, making that difficult to do.

You never wipe out the default Python install,just install a new version using eg Install Python 3.10 or pyenv Simple Python Version Management.
Quick demo using pyenv to install Python 3.101.5 on Mint 19.

tom@tom:~$ pyenv install 3.10.5
Downloading Python-3.10.5.tar.xz...
-> https://www.python.org/ftp/python/3.10.5/Python-3.10.5.tar.xz
Installing Python-3.10.5...
WARNING: The Python lzma extension was not compiled. Missing the lzma lib?
Installed Python-3.10.5 to /home/tom/.pyenv/versions/3.10.5

tom@tom:~$ pyenv global 3.10.5
tom@tom:~$ python -V
Python 3.10.5
# Test pip is build with this Python version,no need to go a repository to get it
tom@tom:~$ pip -V
pip 22.0.4 from /home/tom/.pyenv/versions/3.10.5/lib/python3.10/site-packages/pip (python 3.10) 

Same with the link if build from source(recommended way).

By default, PIP3.10 should be installed, which is the most used package manager for Python

[Skaperen]

i think there may be a bad file mixed in there as a result of carry over from my previous system, that is effectively disrupting the correct operation of access to package files. my thought is that i can find it by purging (the apt term) all the python packages and re-installing them. i have already done a "apt reinstall" and that does not help. i suspect cases where modules cannot be found are cases where the search paths are being altered, especially "/usr/" -> "//".