Hello, I usually use .venv to manage python packages without touching pacman. Everything has worked fine until now, that for any reason, I don’t have any package installed on my virtual environments.
The issue may be fixed by intalling the packages again, but I am a bit concerned about why this could happen.
Notes
pip works, and pip list shows the pacman packages, but pip list --local returns an empty list.
This happens in all virtual environments.
I allow the virtual env to use this flag in the envconfig include-system-site-packages = true, but I don’t think it should interfere.
I am sure I am using the correct path to the python interpreter.
One could guess that your virtual environments has inherited from the system, so when the system got updated to Python 3.14 the system packages moved to Python 3.14 as well.
Yes, I expected that to some extent, but I thought that only applied if there were changes in code to adapt to new interpreter changes. For example, switch statement came at version, 3.10, I thought that will fail if you use 3.9 interpreter on a file made for 3.10.
I searched a bit and you need to install everything again if you dont use a complete isolated environment. I always thought that when you install a package you just download the .py file and if the interpreter understands it, then it is usable at any time, but apparently it is not true for all packages.