[SOLVED] Python 3.10.0 : Problems with pipx

andrew.46 · 10-16-2021, 04:32 AM

I am running -current and have received the Python update to 3.10.0. So now the following is reported:

Code:

andrew@ilium~$ python2 --version
Python 2.7.18
andrew@ilium~$ python3 --version
Python 3.10.0

My pipx installation of eyeD3 broke so I eventually removed the local pipx and went to reinstall as follows:

Code:

python3 -m pip install --user pipx
python3 -m pipx ensurepath
pipx install eyeD3

However this was unsuccessful and I am curious to see if other -current users have the same issue:

Code:

andrew@ilium~$ python3 -m pip install --user pipx
Collecting pipx
  Using cached pipx-0.16.4-py3-none-any.whl (53 kB)
Collecting userpath>=1.6.0
  Using cached userpath-1.7.0-py2.py3-none-any.whl (14 kB)
Collecting argcomplete<2.0,>=1.9.4
  Using cached argcomplete-1.12.3-py2.py3-none-any.whl (38 kB)
Requirement already satisfied: packaging>=20.0 in /usr/lib64/python3.10/site-packages (from pipx) (21.0)
Requirement already satisfied: pyparsing>=2.0.2 in /usr/lib64/python3.10/site-packages (from packaging>=20.0->pipx) (2.4.7)
Collecting click
  Using cached click-8.0.3-py3-none-any.whl (97 kB)
Installing collected packages: click, userpath, argcomplete, pipx
Successfully installed argcomplete-1.12.3 click-8.0.3 pipx-0.16.4 userpath-1.7.0
andrew@ilium~$ python3 -m pipx ensurepath
/usr/bin/python3: No module named pipx

Odd because pipx is there:

Code:

andrew@ilium~$ find . -iname pipx
./.local/bin/pipx
./.local/lib64/python3.10/site-packages/pipx
andrew@ilium~$

and it is appropriately loaded / sourced from my ~/.bashrc:

Code:

# Created by `pipx` on 2021-07-26 09:02:15
export PATH="$PATH:/home/andrew/.local/bin"

Any thoughts?

chrisretusn · 10-16-2021, 09:52 AM

I don't use pip to install anything. I create packages from source.

I did some looking this up.

Perhaps you can upgrade pipx.
https://monovm.com/blog/how-to-upgrade-pip-package/

USUARIONUEVO · 10-16-2021, 03:19 PM

Why no install directly ?

Quote:

pip3 install eyeD3

I install without issues and eye3d works.

lovemeslk · 10-16-2021, 10:28 PM

Quote:

Originally Posted by chrisretusn

I don't use pip to install anything. I create packages from source.

I did some looking this up.

Perhaps you can upgrade pipx.
https://monovm.com/blog/how-to-upgrade-pip-package/

That is really bad advice. You may install local at anytime.
I make a few python-program names for stuff. install to pkg etc etc. the fact is you may install any pip2 pip3
local will not hurt your system. So if slackware down the road actually adds it then the root install is used first . Read the python script son.
It seeks /usr/bin /usr/lib usr/lib64 them ~/.local/bin ~/.local/lib.
Please stop this type of communication.

Test it try to install a local when it is already installed.
Python people seen this issue long time ago.

Python people actually are smart enough to let you install pip as root and bitch about it.
Then if slackware adds it it will override it.

Son these are site scripts no more no less. Pat V with his wild Idea to go to 3.10.0
cause huge work for me for no reason but hey glad it built for him.
3.10.0 will not look for /usr/lib64/python3.9/sites. this cause huge issues.
Hey remember Pat doesn't create python he just packages it woot.

ceed · 10-17-2021, 03:14 AM

I had a bit of trouble with this as well @andrew46.

I may have this completely wrong, however, I would try proceeding as follows:

1. Uninstall pipx and it's dependencies (as well as anything you have installed as --user)
2. delete .local/lib64/python3.9 folder if it's still there
3. perform a pip cache purge
4. proceed as you outline above

I'm not sure if any of my steps are unnecessary or overkill, but, from memory, that is how I solved the same problem you are having.

chrisretusn · 10-17-2021, 04:39 AM

Quote:

Originally Posted by lovemeslk

That is really bad advice. You may install local at anytime.
I make a few python-program names for stuff. install to pkg etc etc. the fact is you may install any pip2 pip3
local will not hurt your system. So if slackware down the road actually adds it then the root install is used first. Read the python script son.
It seeks /usr/bin /usr/lib usr/lib64 them ~/.local/bin ~/.local/lib.
Please stop this type of communication.

Test it try to install a local when it is already installed.
Python people seen this issue long time ago.

Python people actually are smart enough to let you install pip as root and bitch about it.
Then if slackware adds it it will override it.

Son these are site scripts no more no less. Pat V with his wild Idea to go to 3.10.0
cause huge work for me for no reason but hey glad it built for him.
3.10.0 will not look for /usr/lib64/python3.9/sites. this cause huge issues.
Hey remember Pat doesn't create python he just packages it woot.

The OP is using pip to install, so I passed on what I found. I don't use pip. I have no plans to use pip. I install everything from source using SlackBuild scripts. I'm not your son. I will continue to post what I want. Thanks. I'm fine with 3.10, no issues yet.

andrew.46 · 10-17-2021, 07:33 PM

Quote:

Originally Posted by ceed

I had a bit of trouble with this as well @andrew46.

Good to hear that it is not just me

. The steps you outlined did not rectify the issue unfortunately with pipx so I am still working away at the issue...

Edit: I see a few hints here: https://www.linuxquestions.org/quest...th-4175702171/

andrew.46 · 10-17-2021, 08:21 PM

Good to have this issue solved, courtesy of the suggested fix here....

In my case I set PYTHONPATH in ~/.bashrc:

Code:

export PYTHONPATH=${PYTHONPATH}:${HOME}/.local/lib64/python3.10/site-packages

and now the expected behaviour for local Python installation with both pip3 and pipx is as it was previously. Thanks to all who have looked at this issue...

Code:

andrew@ilium~$ pipx list
venvs are in /home/andrew/.local/pipx/venvs
apps are exposed on your $PATH at /home/andrew/.local/bin
   package eyed3 0.9.6, Python 3.10.0
    - eyeD3
andrew@ilium~$