#16466: Add gambit as an optional package
-------------------------------------+-------------------------------------
       Reporter:  jcampbell          |        Owner:
           Type:  enhancement        |       Status:  needs_work
       Priority:  major              |    Milestone:  sage-6.4
      Component:  packages:          |   Resolution:
  optional                           |    Merged in:
       Keywords:                     |    Reviewers:  Thierry Monteil,
        Authors:  James Campbell,    |  Karl-Dieter Crisman, Travis
  Vince Knight                       |  Scrimshaw
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  u/vinceknight/gambit               |  2227a00a447fdc320970ed5a7824340dacd54ec1
   Dependencies:                     |     Stopgaps:
-------------------------------------+-------------------------------------

Comment (by vinceknight):

 Replying to [comment:53 kcrisman]:
 > Okay, I think this is fine, except for a few minor issues.
 > * Add to reference manual?

 I tried doing this but conscious to not actually want to import
 `gambit.py` as a Sage module, I only wanted to add it to the relevant
 `index.rst`. When trying to build the docs though I got an error:

 {{{
 [game_theo]
 
/Users/vince/sage/src/doc/en/reference/game_theory/sage/game_theory/gambit.rst:11:
 WARNING: autodoc can't import/find module 'sage.game_theory.gambit', it
 reported error: "No module named gambit", please check your spelling and
 sys.path
 }}}

 This makes me think that I also need to link gambit.py as a library _which
 I don't want to do_ (especially named as it is). Am I missing something:
 is there a best way to do this or should we just leave it as it is? So
 that it is in essence 'for developers'?

 > * Please recheck for duplication like
 > {{{
 > +    In [1]: g = gambit.Game.new_table([2,2])
 > +    In [2]: g = gambit.Game.new_table([2,2])
 > }}}

 Have checked through.

 > * I have a feeling that if this is added to reference, there will be a
 hiccup here.
 > {{{
 > +Here is a list of various other solvers that can be used:
 > +
 > +- ExternalEnumPureSolver
 > +- ExternalEnumMixedSolver
 > +- ExternalLPSolver
 > +- ExternalLCPSolver
 > +- ExternalSimpdivSolver
 > +- ExternalGlobalNewtonSolver
 > +- ExternalEnumPolySolver
 > +- ExternalLyapunovSolver
 > +- ExternalIteratedPolymatrixSolver
 > +- ExternalLogitSolver
 > +
 > +    In [22]: solver = gambit.nash.ExternalEnumPureSolver()
 > +    In [23]: solver.solve(g)
 > +    Out[23]: [<NashProfile for '': [Fraction(0, 1), Fraction(1, 1),
 Fraction(0, 1), Fraction(1, 1)]>]
 > +
 > }}}
 >    Because there is what is intended to be a literal block after a list.
 You should have another sentence explaining it and then the usual double
 colon.

 Yup: have fixed.

 > * You will need to add `import gambit` before each of your Ipython
 examples, otherwise they don't work.

 Woops: yup have added those in.

--
Ticket URL: <http://trac.sagemath.org/ticket/16466#comment:58>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to