On Thu, Oct 29, 2015 at 10:12 AM, Nathann Cohen <[email protected]> wrote:
>> Yep! That's why I called it "not tested". In my opinion, the only
>> reasonable change would be
>>
>> " # not tested" ----> " # broken"
>>
>> That would probably create an even more accurate impression.
>
> I flagged many doctests with 'not tested' because running them would
> take 10+s per function (and there are many of them). Those functions
> take no input whatsoever, and are just meant to return a big object
> (examples in graphs/strongly_regular_db).
That's what
# long time
is supposed to be for.
>
> The same happens for some doctests that rely on optional LP solvers:
> they can take <1s with CPLEX/Gurobi, but 'standard sage' (with GLPK)
> cannot be expected to ever solve them.
So if a user tries to use them they will be effectively broken?
> I also see calls to 'graph_editor' flagged as 'not tested' in the
> graph/ folder, but as I do not know this code I cannot tell the
> reason.
It's a graphical editor that runs in a web browser. (Or at least it
was 7 years ago...)
>
> Nathann
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" 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-devel.
> For more options, visit https://groups.google.com/d/optout.
--
William (http://wstein.org)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" 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-devel.
For more options, visit https://groups.google.com/d/optout.
