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.15:30:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1397230240.59.0.389621451221.issue21197@psf.upfronthosting.co.za>
In-reply-to
Content
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).

Clearly, if the idea is to support Pythons patched by distros, then it seems that there is little alternative available apart from the symlink.

As you say, lib64 should be the symlink name, pointing to the lib directory.  Should the symlink be created on 64-bit Linux venvs on all POSIX platforms, and should OS X be excluded?
History
Date User Action Args
2014-04-11 15:30:40vinay.sajipsetrecipients: + vinay.sajip, pitrou, BinaryKhaos
2014-04-11 15:30:40vinay.sajipsetmessageid: <1397230240.59.0.389621451221.issue21197@psf.upfronthosting.co.za>
2014-04-11 15:30:40vinay.sajiplinkissue21197 messages
2014-04-11 15:30:39vinay.sajipcreate