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 mishikal
Recipients eric.araujo, lemburg, mishikal, r.david.murray
Date 2013-12-13.18:30:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1386959416.87.0.142042542431.issue19968@psf.upfronthosting.co.za>
In-reply-to
Content
Ok, so the general idea is to be able to install your software in a specific location and then symlink it back into another location (like /usr/local).  This allows quick and easy software version swapping.  I've used it to do things like test mariadb vs mysql, or various builds of openldap.  It works well with perl too.

The issue I'm hitting here with python is with site packages.  I wanted to be able to install the specific versions of various modules into their own location, and link then back via stow, but python can't find them since the site path is the literal location of the install instead of the symlink'd location.  I ended up just installing the modules into the default python location to get around it by now, but it means I can't trivially swap out different versions the python modules now.
History
Date User Action Args
2013-12-13 18:30:16mishikalsetrecipients: + mishikal, lemburg, eric.araujo, r.david.murray
2013-12-13 18:30:16mishikalsetmessageid: <1386959416.87.0.142042542431.issue19968@psf.upfronthosting.co.za>
2013-12-13 18:30:16mishikallinkissue19968 messages
2013-12-13 18:30:16mishikalcreate