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 it the base directories of the venvs and it 
constructs the appropriate path to the site-packages and uses those internally. 
Rightfully, it assumes a lib/ directory to contain everything which works just 
fine for virtualenv created venvs due to the symlink but not for venv created 
venvs.

@ned.deily: I know what you mean. And I am very inclined to fully agree with 
you that dists should patch this as well. But the problem I see with this is: 
Except for Debian-based dists, all of the other major ones  (Gentoo, 
Fedora/RedHat/CentOS, OpenSUSE, ...) and their derivatives, put Python under 
lib64/ on multilib systems. And the patches they use and the changes they 
introduce already differ here and there in important key details. It would be 
no different with this issue as well. Besides, this scenario (Python under 
lib64/) is not so uncommon anymore and imho, should be supported by Python out 
of the box by making those things properly configurable during compilation. But 
that is a different subject altogether.

IMHO, this feature is small enough to be added to Python's venv to standardize 
it across dists. Besides, it makes it more compatible and a better drop-in 
replacement for virtualenv itself.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue21197>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to