This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author BinaryKhaos
Recipients BinaryKhaos
Date 2014-04-10.13:50:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
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 lib will remain empty. For some third party apps, this is confusing.

virtualenv, for example, installs a lib64 symlink to lib automatically. IMHO, more correctly would be a lib to lib64 symlink.
Date User Action Args
2014-04-10 13:50:32BinaryKhaossetrecipients: + BinaryKhaos
2014-04-10 13:50:32BinaryKhaossetmessageid: <>
2014-04-10 13:50:32BinaryKhaoslinkissue21197 messages
2014-04-10 13:50:32BinaryKhaoscreate