Great, thank you!
Am Freitag, 24. Mai 2019 01:05:04 UTC+2 schrieb Travis Scrimshaw:
>
> sage -t --verbose (or -tp of course)
>
> Best,
> Travis
>
>
> On Friday, May 24, 2019 at 4:20:39 AM UTC+10, Martin R wrote:
>>
>> One thing I would like very much is the possibility to find out more
>>
There is also the "warn-long" flag:
sage -t --warn-long 3.2 FILE
should tell you all tests in FILE that take more than 3.2 seconds.
On Thursday, May 23, 2019 at 4:05:04 PM UTC-7, Travis Scrimshaw wrote:
>
> sage -t --verbose (or -tp of course)
>
> Best,
> Travis
>
>
> On Friday, May 24,
sage -t --verbose (or -tp of course)
Best,
Travis
On Friday, May 24, 2019 at 4:20:39 AM UTC+10, Martin R wrote:
>
> One thing I would like very much is the possibility to find out more
> precisely which doctests within a module take a long time...
>
> Or is this possible already?
>
> Martin
One thing I would like very much is the possibility to find out more
precisely which doctests within a module take a long time...
Or is this possible already?
Martin
Am Donnerstag, 23. Mai 2019 19:00:36 UTC+2 schrieb vdelecroix:
>
> Very fancy :-) I would definitely appreciate it if there.
Very fancy :-) I would definitely appreciate it if there. Though,
I would not put it on top of my list of most wanted things.
Vincent
Le 23/05/2019 à 18:40, E. Madison Bray a écrit :
Something I've wanted for a long time in the Sage doctest runner is
progress bars, so I hacked up a prototype
Something I've wanted for a long time in the Sage doctest runner is
progress bars, so I hacked up a prototype (see screenshot). It works
even with parallel docbuilds.
I think there are still some bugs and other kinks to work out so it
will take a little more time to get this really polished up,
