On Tue, Jun 27, 2017 at 03:41:27PM +0200, Gudrun Amedick wrote:

i ran into that too (on debian 8). I'm not that familiar with virtual 
environments but this is what I found out.

It looks like the virtual environment doesn't get activated properly in the 
shipped ini.d-file (it is the shipped one, right?).
If I add ". /path/to/.venv/bin/activate" to it, everything runs just fine. 
"run.sh" has this line. The init.d-file hasn't. It just calls the .venv-
python directly. It seems like that's not fully equivalent to activating .venv 
and running python in there. I don't really know why. I'm guessing

Hope that helps a bit.

      Gudrun Amedick


The thing is that running the python interpreter in the virtual
environment _should_ take care of that anyway. The provided debian init
script even says as much:  "A simple way to activate this virtualenv is
to use the python interpreter in <GALAXY_DIR>/.venv".

In any case, explicitly activating the virtualenv solves the problem.
Thanks for the pointer Gudrun.

Maybe a dev can chime in here.

Many Thanks


Un o’r 4 prifysgol uchaf yn y DU a’r orau yng Nghymru am fodlonrwydd myfyrwyr.
(Arolwg Cenedlaethol y Myfyrwyr 2016)

Top 4 UK university and best in Wales for student satisfaction
(National Student Survey 2016)
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