Matthias Dahl added the comment:
@vinay.sajip: No problem. Jedi is a auto-completion library. It does not add
any links anywhere. It naturally has to know about which venvs you use so it
can find all modules and their sources to process them. Thus, you (or the
implementation using Jedi) pass
Matthias Dahl added the comment:
The problem is: Some Linux dists install Python under /usr/lib64 on a multilib
systems and patch Python accordingly, e.g. Gentoo or Fedora. Thus, Python looks
for lib64/pythonX.Y/... which is also why pip installs to lib64/... by default
on those systems
Matthias Dahl added the comment:
Take for example the case that you have to juggle with several venvs and mix
them together. This has happened to me in the past in very legitimate cases.
You have to add those venvs to the path yourself. I am not talking about having
a shell where you do your
New submission from Matthias Dahl:
Creating a new venv on a multilib system does not install an appropriate link
from lib to lib64 or the other way around. Currently, venv creates a single lib
dir, but everything installed with pip within the venv, will be installed to
lib64/... instead while
