[issue21197] venv does not create lib64 directory and appropriate symlinks

Vinay Sajip added the comment: > The added 64-bit test unnecessary adds an import for struct. I corrected this when fixing #21643. -- ___ Python tracker ___

[issue21197] venv does not create lib64 directory and appropriate symlinks

Ned Deily added the comment: The added 64-bit test unnecessary adds an import for struct. The documented preferred test is: sys.maxsize > 2**32 https://docs.python.org/dev/library/platform.html#platform.architecture -- ___ Python tracker

[issue21197] venv does not create lib64 directory and appropriate symlinks

Vinay Sajip added the comment: Issue #18807 relates to symlinks not being available, or not being wanted by the user creating the environment. The lib64 symlink is (currently) the only case where we symlink to a directory (in the other cases, such as aliases for the interpreter, we can use cop

[issue21197] venv does not create lib64 directory and appropriate symlinks

Roundup Robot added the comment: New changeset 4d9b24b2f1b8 by Vinay Sajip in branch '3.4': Issue #21197: Add lib64 -> lib symlink in venvs on 64-bit non-OS X POSIX. http://hg.python.org/cpython/rev/4d9b24b2f1b8 New changeset 947515cc8957 by Vinay Sajip in branch 'default': Closes #21197: Add li

[issue21197] venv does not create lib64 directory and appropriate symlinks

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 i

[issue21197] venv does not create lib64 directory and appropriate symlinks

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue21197] venv does not create lib64 directory and appropriate symlinks

Ned Deily added the comment: "should OS X be excluded?" Yes. OS X uses universal binaries, with multiple CPU archs automatically combined at build time into one file, so there generally is no need for arch-specific directories. But if the problem is being caused by Pythons patched by third-pa

[issue21197] venv does not create lib64 directory and appropriate symlinks

Vinay Sajip added the comment: Thanks for the info. I'm not opposed to adding a symlink on POSIX systems - I just wanted to make sure that was the right solution. My comment about adding links willy-nilly was about tools like Jedi that you mentioned (perhaps I misunderstood how it works). Cl

[issue21197] venv does not create lib64 directory and appropriate symlinks

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. This

[issue21197] venv does not create lib64 directory and appropriate symlinks

Vinay Sajip added the comment: What does pip do under Windows? The symlink feature doesn't work on all Windows versions and is not quite the same as on POSIX. What is it that actually requires lib64? As venvs are specific to a single interpreter, it seems like it is inherently not a good idea

[issue21197] venv does not create lib64 directory and appropriate symlinks

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 w

[issue21197] venv does not create lib64 directory and appropriate symlinks

Antoine Pitrou added the comment: Which third party apps are these? AFAIK, venv's directory layout is private - it shouldn't be "interpreted" by other programs (as opposed to the system-level lib/lib64 layout). -- nosy: +pitrou, vinay.sajip ___ Pyth

[issue21197] venv does not create lib64 directory and appropriate symlinks

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