Re: [sage-devel] Re: bug in modular/pollack_stevens/modsym.py --> stopgap

2017-05-15 Thread Vincent Delecroix
Thanks Marc for your answer! It would be very useful to have explicitely mentioned in the documentation of these functions that the result is not constant over time (ie explain what consistency the user is supposed to expect). Looking at the name "is_ordinary", I do not suspect it to be depende

[sage-devel] Thumbnail gallery

2017-05-15 Thread William Stein
Hi, Has anybody made something like https://matplotlib.org/gallery.html for Sage's plotting? It' gets tiring constantly referring people to "the chapters on 2d and 3d graphics in the sage reference manual": http://doc.sagemath.org/html/en/reference/index.html#graphics I mean the reference manu

[sage-devel] Re: bug in modular/pollack_stevens/modsym.py --> stopgap

2017-05-15 Thread Marc Masdeu
The function ps_modsym_from_simple_modsym_space calls internally a randomized method from modular symbols (dual_eigenvector). Here is a snippet of code that also returns different answers depending on the seed (on a fresh session, since dual_eigenvector gets cached). f = Newforms(32, 8, names='

Re: [sage-devel] Sage policy question: require docstrings and doctests?

2017-05-15 Thread Erik Bray
On Mon, May 15, 2017 at 5:26 PM, William Stein wrote: > On Mon, May 15, 2017 at 6:56 AM, Erik Bray wrote: > [...] >> In PEP-8, Python's style guide for Python code, there's an admonition >> right at the beginning titled "A Foolish Consistency is the Hobgoblin >> of Little Minds" (the wording is t

Re: [sage-devel] Sage policy question: require docstrings and doctests?

2017-05-15 Thread William Stein
On Mon, May 15, 2017 at 6:56 AM, Erik Bray wrote: [...] > In PEP-8, Python's style guide for Python code, there's an admonition > right at the beginning titled "A Foolish Consistency is the Hobgoblin > of Little Minds" (the wording is tongue-in-cheek; don't take it > literally!): https://www.pytho

[sage-devel] bug in modular/pollack_stevens/modsym.py --> stopgap

2017-05-15 Thread Vincent Delecroix
Dear all, I am worried about a consequence of my cleaning in matrix_rational_dense at [1]. It appears that an innocent doctest in modular/pollack_stevens/modsym.py depends on the seed of the random generators where it should not be, see [2]. I tested a lot more than it used to be the code in

Re: [sage-devel] Sage policy question: require docstrings and doctests?

2017-05-15 Thread Erik Bray
On Wed, May 10, 2017 at 1:42 PM, Michael Orlitzky wrote: > On 05/09/2017 03:14 PM, John H Palmieri wrote: >> Sage's developer's guide says: "Every function must have a docstring" >> which must include "An EXAMPLES block for examples. This is not >> optional." What is meant by "function"? Here is a

Re: [sage-devel] cryptominisat 2 -> 5 jump (+ test cmake)

2017-05-15 Thread Travis Scrimshaw
The latest version of chomp will also need cmake. So I'm +1 for making it optional (where as a dependency, the spkg is built only when there is not a system installation). Best, Travis -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscr

[sage-devel] Re: Error installing Cython: pip2 was not found?

2017-05-15 Thread Travis Scrimshaw
Glad to hear it worked. :) Best, Travis On Sunday, May 14, 2017 at 10:10:43 AM UTC-5, Peleg Michaeli wrote: > > Hi Travis, > > Thanks, it helped (took 5 hours, but helped :)) > > On Friday, 12 May 2017 17:11:28 UTC+3, Travis Scrimshaw wrote: >> >> The gcc that is included in Sage is 5.4.0, so I'

Re: [sage-devel] cryptominisat 2 -> 5 jump (+ test cmake)

2017-05-15 Thread Dima Pasechnik
On Sunday, May 14, 2017 at 10:17:52 PM UTC+1, François wrote: > > I am confident cmake can now be moved to optional. I took care > of all of the problems I could see on OS X and helped with the > ones on other platforms. > Do we need some kind of vote for moving from experimental to > optiona