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 vinay.sajip
Recipients BinaryKhaos, pitrou, vinay.sajip
Date 2014-04-11.10:08:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1397210915.58.0.952182933016.issue21197@psf.upfronthosting.co.za>
In-reply-to
Content
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 to add site-package links to venvs in other venvs willy-nilly, though of course it would work in homogeneous scenarios.

Do we know *why* virtualenv added a lib64 symlink? What (apart from possibly pip) fails if it doesn't do this? Does distutils require it?
History
Date User Action Args
2014-04-11 10:08:35vinay.sajipsetrecipients: + vinay.sajip, pitrou, BinaryKhaos
2014-04-11 10:08:35vinay.sajipsetmessageid: <1397210915.58.0.952182933016.issue21197@psf.upfronthosting.co.za>
2014-04-11 10:08:35vinay.sajiplinkissue21197 messages
2014-04-11 10:08:35vinay.sajipcreate