[sage-devel] Warn about long doctests (#16609 needs review)

2014-07-28 Thread Volker Braun
A small handful of modules takes the majority of the doctest walltime, see e.g. this lopsided distribution: I'm proposing to * turn the existing sage -t --warn-long parameter into a warning (instead of an error) * enable it by defau

Re: [sage-devel] Re: hiding doctest in documentation

2014-07-28 Thread William Stein
On Jul 28, 2014 8:47 AM, "Volker Braun" wrote: > > On Monday, July 28, 2014 11:42:05 AM UTC-4, William wrote: >> >> That said, there is a ready-made solution [1] for exactly the original >> question, > > > The TESTS: section does appear in the reference manual, fyi. Its just a way to separate it o

Re: [sage-devel] Re: hiding doctest in documentation

2014-07-28 Thread Volker Braun
On Monday, July 28, 2014 11:42:05 AM UTC-4, William wrote: > > That said, there is a ready-made solution [1] for exactly the original > question, > The TESTS: section does appear in the reference manual, fyi. Its just a way to separate it off from EXAMPLES: Specifically for dictionaries we also

Re: [sage-devel] Re: hiding doctest in documentation

2014-07-28 Thread William Stein
On Mon, Jul 28, 2014 at 8:24 AM, Simon King wrote: > Hi Daniel, > > On 2014-07-28, Daniel Krenn wrote: >> Background: The output of a doctest is a dictionary; therefore there is >> some uncertainty about the ordering of the entires. To have the >> dict-output, but get tested as well, I want to do

[sage-devel] Re: hiding doctest in documentation

2014-07-28 Thread Simon King
Hi Daniel, On 2014-07-28, Daniel Krenn wrote: > Background: The output of a doctest is a dictionary; therefore there is > some uncertainty about the ordering of the entires. To have the > dict-output, but get tested as well, I want to do the following: > > sage: dict = {'a': 'b', 'x': 'y'} # ran

[sage-devel] Re: hiding doctest in documentation

2014-07-28 Thread Volker Braun
On Monday, July 28, 2014 9:42:16 AM UTC-4, Daniel Krenn wrote: > > Is there a way to hide a doctest in the documentation, but still keep it > in the source, so that it will get tested? > No. It wouldn't be a "doc"test then, would it? > sage: dict = {'a': 'b', 'x': 'y'} # random > {'a': 'b',

[sage-devel] hiding doctest in documentation

2014-07-28 Thread Daniel Krenn
Is there a way to hide a doctest in the documentation, but still keep it in the source, so that it will get tested? Background: The output of a doctest is a dictionary; therefore there is some uncertainty about the ordering of the entires. To have the dict-output, but get tested as well, I want to

[sage-devel] FiniteStateMachines: naming conventions of classes

2014-07-28 Thread Daniel Krenn
Dear all, in the finite_state_machine module there exist classes FSMState, FSMTransition, FSMProcessIterator. The process iterator is to be written new, see http://trac.sagemath.org/ticket/16538 Thereby, the following questions arose: What are the naming conventions here w.r.t. the prefix "FSM", i

Re: [sage-devel] Re: "Groups" in Sage

2014-07-28 Thread Nathann Cohen
Yo ! > Until all properties of graphs are known to Sage, you should then be pushing > to not have any graph in Sage. ... Okay, when we have reached this level of non-communication there is nothing to add. Nathann -- You received this message because you are subscribed to the Google Groups