Suggestions for eventually updating where Python3 packages are installed via pip? about ptf HOT 2 OPEN

It looks like the same error occurs when using pip install --user ... instead of sudo pip install ....
IMO the best option would be to use pipx as suggested, or a virtual env that you manage directly.
Or you can just export PIP_BREAK_SYSTEM_PACKAGES=1 in the correct profile file, and then forget about it. You won't have to use --break-system-packages explicitly every time, and you can keep using pip as before.

from ptf.

I did not know about the environment variable PIP_BREAK_SYSTEM_PACKAGES.

From some experimentation on an Ubuntu 23.04 system, it seems that only works if I use sudo -E pip install ..., so it is just as troublesome in requiring that all install scripts are edited, as any of the other methods you mention.

I may see what it takes to remove the sudo from all of the sudo pip3 ... commands everywhere from all p4lang install scripts in my local copies -- there probably aren't more than half a dozen or so occurrences.

from ptf.