Re: [sage-devel] Re: How to handle an optional package that causes build crashes

2014-06-13 Thread Volker Braun
On Friday, June 13, 2014 1:52:58 PM UTC+1, Vincent Knight wrote: > > from sage.misc.package import is_package_installed > from cooperative_game import CooperativeGame > if is_package_installed('gambit'): > from normal_form_game import * > > normal_form_game.py is the module that imports and inh

Re: [sage-devel] Re: How to handle an optional package that causes build crashes

2014-06-13 Thread Nathann Cohen
Hello !! > We've actually just thought of a completely different approach that we > _might_ or _might not_ go with. There are advantages (which include not > having to deal with this problem at all) and disadvantages that we need to > carefully consider (if it's of interest the idea is here: >

Re: [sage-devel] Re: How to handle an optional package that causes build crashes

2014-06-13 Thread Vincent Knight
On 13 June 2014 12:21, Nathann Cohen wrote: > I cheated in all cases : > > For the optinal LP solvers I don't mind as there is a standard LP > solver that exposes the features : > > http://www.sagemath.org/doc/reference/numerical/index.html > > For the C libraries solving specfic graph problem th

Re: [sage-devel] Re: How to handle an optional package that causes build crashes

2014-06-13 Thread Nathann Cohen
> Very helpful: thanks. Is there another way to handle this and/or get around > it? I cheated in all cases : For the optinal LP solvers I don't mind as there is a standard LP solver that exposes the features : http://www.sagemath.org/doc/reference/numerical/index.html For the C libraries solvin

Re: [sage-devel] Re: How to handle an optional package that causes build crashes

2014-06-13 Thread Vincent Knight
On 13 Jun 2014 12:59, "Nathann Cohen" wrote: >>> >>> Look at the bottom of src/module_list.py, there are already a number of Cython extensions that are only compiled conditionally. >> >> >> Thanks! > > > Keep something in mind, however : all the documentation contained in those files will *not* ap

Re: [sage-devel] Re: How to handle an optional package that causes build crashes

2014-06-13 Thread Nathann Cohen
> > Look at the bottom of src/module_list.py, there are already a number of >> Cython extensions that are only compiled conditionally. >> > > Thanks! > Keep something in mind, however : all the documentation contained in those files will *not* appear in Sage's online doc. Which means that users

Re: [sage-devel] Re: How to handle an optional package that causes build crashes

2014-06-13 Thread Vincent Knight
On 13 June 2014 11:40, Volker Braun wrote: > I take it you are trying to write a Cython class using a shared library > from the Gambit optional package? > That's correct :) > > Look at the bottom of src/module_list.py, there are already a number of > Cython extensions that are only compiled co