Hi all,

Last week at the Galaxy Admins video hangout Nate gave an
overview of the way Python dependency handling is changing
from using egg files to using wheel files instead - slide links at:


I understand the Galaxy v16.01 (2016 January feature freeze)
release which switches from eggs to wheels is due out shortly -
hopefully this week?

Recently we've been trying to setup a replacement Galaxy instance
where jobs are submitted to our SGE cluster as the linux user
requesting the job. This has been a bumpy road, e.g.


Right now we've run into a problem with the metadata scripts
trying to access ~/.python-eggs and going back over the archives
it looks like we may need to set $PYTHON_EGG_CACHE to a
temp folder on a per-node per-user basis, see e.g.


Sadly the wiki does not cover this aspect of running jobs as the
real user (but the egg settings are about to be obsolete):


Clearly with Galaxy v16.01 the eggs and $PYTHON_EGG_CACHE
will go away. What happens with wheels, Python virtual environments,
and running jobs as the real user?


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