#3231: Use the randgen framework to set the seeds for controlled Magma, 
Singular,
etc. sessions
-------------------------------------+-------------------------------------
       Reporter:  malb               |        Owner:  cwitty
           Type:  enhancement        |       Status:  needs_work
       Priority:  minor              |    Milestone:  sage-6.4
      Component:  interfaces         |   Resolution:
       Keywords:                     |    Merged in:
        Authors:  Travis Scholl      |    Reviewers:  Martin Albrecht
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  u/tscholl2/seeds_3231              |  773a1f300096fb5c40cf4375f805375edd5cbf09
   Dependencies:                     |     Stopgaps:
-------------------------------------+-------------------------------------

Comment (by tscholl2):

 I get the first 3 errors if I run `sage -t --long
 src/sage/interfaces/magma.py` but not if I run `./sage -t --long
 src/sage/interfaces/magma.py`. Shouldn't I only be checking if it runs
 with the version of Sage on the branch and not the user's systems'
 version?

 The last error seems to be something I didn't notice. Apparently some of
 the interfaces keep a counter of the commands used and label things with
 it. The `set_seed` function for some interfaces raises this counter
 because it needs to call a command in the interface. So running the test
 in `src/sage/repl/interpreter.py` the counter is off from what it used to
 be.

 This error doesn't occur if I comment out line 626 in
 `src/sage/interfaces/maxima.py`:
 {{{
 625 # set random seed
 626 self.set_seed(self._seed)
 }}}

 I'm not sure what to do about this. It seems like there is a few options:

 * We could reset the counter after the `set_seed` function is called (I
 actually don't know if this is possible yet).
 * We could change all the doc tests in functions which use this counter
 and increment it manually.
 * We could not run `set_seed` on start and leave it up to the user to run
 it.

 Martin, do you have any suggestions on which way to proceed?

--
Ticket URL: <http://trac.sagemath.org/ticket/3231#comment:30>
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