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, eric.araujo, ned.deily, pitrou, python-dev, vinay.sajip
Date 2014-05-28.06:43:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1401259403.95.0.268665138221.issue21197@psf.upfronthosting.co.za>
In-reply-to
Content
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 copies rather than symlinks). I propose to make a change such that if copying rather than symlinking is specified, the lib64 link simply isn't created - a copy would be of no use here.
History
Date User Action Args
2014-05-28 06:43:24vinay.sajipsetrecipients: + vinay.sajip, pitrou, ned.deily, eric.araujo, python-dev, BinaryKhaos
2014-05-28 06:43:23vinay.sajipsetmessageid: <1401259403.95.0.268665138221.issue21197@psf.upfronthosting.co.za>
2014-05-28 06:43:23vinay.sajiplinkissue21197 messages
2014-05-28 06:43:22vinay.sajipcreate