Hello Nate,
On May 14, 2013, at 10:58 AM, John Chilton wrote:
Hey Nate,
On Tue, May 14, 2013 at 8:40 AM, Nate Coraor n...@bx.psu.edu wrote:
Hi John,
A few of us in the lab here at Penn State actually discussed automatic
creation of virtualenvs for dependency installations a
John,
Could you create a pull request with your changes from the branch in github?
I'll accept them and then commit my additions and changes. Today is the
freeze so I'd like to get this in to the next release.
Thanks,
---nate
On May 17, 2013, at 11:21 AM, John Chilton wrote:
Hey All,
Done.
On the topic of the freeze, if Dannon's change requiring all metadata
to be set externally is going to be included I would suggest someone
looking at build_command_line in runners/__init__.py.
Hey All,
There was a long conversation about this topic in IRC yesterday (among
people who don't actually use the tool shed all that frequently), I
have posted it to the new unofficial Galaxy Google+ group if anyone
would like to read and chime in.
Hey Nate,
On Tue, May 14, 2013 at 8:40 AM, Nate Coraor n...@bx.psu.edu wrote:
Hi John,
A few of us in the lab here at Penn State actually discussed automatic
creation of virtualenvs for dependency installations a couple weeks ago.
This was in the context of Bjoern's request for supporting
Hi John,
A few of us in the lab here at Penn State actually discussed automatic creation
of virtualenvs for dependency installations a couple weeks ago. This was in
the context of Bjoern's request for supporting compile-time dependencies. I
think it's a great idea, but there's a limitation
On May 14, 2013, at 10:58 AM, John Chilton wrote:
Hey Nate,
On Tue, May 14, 2013 at 8:40 AM, Nate Coraor n...@bx.psu.edu wrote:
Hi John,
A few of us in the lab here at Penn State actually discussed automatic
creation of virtualenvs for dependency installations a couple weeks ago.
Greg created the following card, and I'm working on a few changes to your
commit:
https://trello.com/card/toolshed-consider-enhancing-tool-dependency-definition-framework-per-john-chilton-s-pull-request/506338ce32ae458f6d15e4b3/848
Thanks,
--nate
On May 14, 2013, at 1:45 PM, Nate Coraor wrote:
On Tue, Apr 16, 2013 at 2:46 PM, John Chilton chil...@msi.umn.edu wrote:
Stepping back a little, is the right way to address Python
dependencies?
Looks like I missed this thread, hence:
http://lists.bx.psu.edu/pipermail/galaxy-dev/2013-April/014169.html
I was a big advocate for
Hi Greg.
If numpy is not required for compiling matplotlib components (i.e.,
matplotlib components just use numpy after installation),
then you should be able to make this work using a complex repository
dependency for numpy in your tool_dependencies.xml definition for
Stepping back a little, is the right way to address Python
dependencies? I was a big advocate for inter-repository dependencies,
but I think taking it to the level of individual python packages might
be going too far - my thought was they were needed for big 100Mb
programs and stuff like that. At
Hi,
is there a general rule to handle dependencies inside of
tool_dependencies.xml?
Lets assume I write a matplotlib orphan tool_dependencies.xml file.
matplotlib depends on numpy. Numpy has already a orphan definition.
Is there a way to include numpy as dependency inside the
Hi Greg,
If numpy is not required for compiling matplotlib components (i.e.,
matplotlib components just use numpy after installation),
then you should be able to make this work using a complex repository
dependency for numpy in your tool_dependencies.xml definition for matplotlib.
The
Hi Björn,
On Apr 15, 2013, at 6:31 PM, Björn Grüning wrote:
Hi Greg,
If numpy is not required for compiling matplotlib components (i.e.,
matplotlib components just use numpy after installation),
then you should be able to make this work using a complex repository
dependency for numpy
14 matches
Mail list logo
