On Nov 18, 2014 7:26 AM, "John Chilton" <jmchilton@gmail.com> wrote:
I will admit to not actually understanding Galaxy's dependency management but I think virtualenv is exactly the advice people who do understand it give http://dev.list.galaxyproject.org/Local-installation-problem-td4662627.html. It is a widely used tool precisely designed to solve such problems - I think it is the best way to go. I don't know why it would not be appropriate for existing installations - I think it is in fact somethimg of a "best practice" for existing installations.
Our existing installation is not using a virtual env, and I fear switching to that could be disruptive.
Certainly that error message should be more helpful but I am not sure we should do anything to address this beyond that - do you have a particular idea in mind?
Not show the IndexError exception? :P Here the user should be told something about a conflict between MarkupSafe and paramiko (assuming this is the real problem). Peter