Message215883
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:32 | BinaryKhaos | set | recipients:
+ BinaryKhaos |
2014-04-10 13:50:32 | BinaryKhaos | set | messageid: <1397137832.25.0.881871760177.issue21197@psf.upfronthosting.co.za> |
2014-04-10 13:50:32 | BinaryKhaos | link | issue21197 messages |
2014-04-10 13:50:32 | BinaryKhaos | create | |
|