After upgrading from the October 2014 release to 15.03 we started
experiencing job failures for one of our custom tools, which I eventually
tracked down to PYTHONPATH now being set in the job environment to
$GALAXY_HOME/lib. The dependencies for this tool are installed in a
virtualenv that is activated by the tool dependency package's It
looks like one of the scripts in this virtualenv attempts to use setuptools
to find its dependencies, but because of the PYTHONPATH setting ends up in
Galaxy's $GALAXY_HOME/lib/

Traceback (most recent call last):
line 8, in <module>
    from pkg_resources import load_entry_point
line 2603, in <module>
line 666, in require
    needed = self.resolve(parse_requirements(requirements))
line 565, in resolve
    raise DistributionNotFound(req)  # XXX put more info here
pkg_resources.DistributionNotFound: pytz>=2011k

I worked around this issue by prepending the virtualenv's
lib/python2.7/site-packages directory to PYTHONPATH in the tool dependency
package's, but I'm a bit confused why this is now necessary. Can
anyone shed some light on what changed?



Brian Claywell | programmer/analyst
Matsen Group   | <>
Fred Hutchinson Cancer Research Center
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:

To search Galaxy mailing lists use the unified search at:

Reply via email to