Thu 2019-05-23 16:41:04 UTC, E. Madison Bray:
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
>
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
> configure: error: source directory already configured; run "make
distclean" there first
Is this the make distclean of sage or the make distclean of pynormaliz?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this
Is this the make distclean of SAGE or some make distclean for pynormaliz
only?
On Thursday, May 23, 2019 at 11:07:54 PM UTC+2, vdelecroix wrote:
>
> So the PyNormaliz configure script is actually working... you strangely
> obtained an error when it was run via the setup.py script with the
>
So the PyNormaliz configure script is actually working... you strangely
obtained an error when it was run via the setup.py script with the
mysterious
configure: error: source directory already configured; run "make
distclean" there first
Vincent
Le 23/05/2019 à 23:04, Sébastien Labbé a
$ cd /home/slabbe/GitBox/sage/local/var/tmp/sage/build/pynormaliz-2.5/src
$ sage -sh
Starting subshell with Sage environment variables set. Don't forget
to exit when you are done. Beware:
* Do not do anything with other copies of Sage on your system.
* Do not use this for installing Sage
This line in your log is also very suspicious
{{{
configure: error: source directory already configured; run "make
distclean" there first
}}}
It comes from the Sage main configure script. It seems that your
install suffers some inconsistencies.
Vincent
Le 23/05/2019 à 22:55, Sébastien
Salut,
Could you try running manually (in the tmp build repo of pynormaliz)
$ sage -sh
$ ./configure
Le 23/05/2019 à 22:55, Sébastien Labbé a écrit :
Bonsoir,
As I reported in sage-release for 8.8.beta6 [1], I get troubles installing
pynormaliz. I pasted the log on framabin here [2]. I am
Bonsoir,
As I reported in sage-release for 8.8.beta6 [1], I get troubles installing
pynormaliz. I pasted the log on framabin here [2]. I am running Ubuntu
16.04.
The discussion started on the closed ticket #27731 [3], but it is better to
continue it on sage-devel.
Sébastien
[1]
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,
I can live with (V, projections, coprojections)
but I dislike hiding everything in lists (or lists of lists, or lists of
lists of lists..).
Being able to type VW.projections(1) would just be so much nicer.
--
You received this message because you are subscribed to the Google Groups
14 matches
Mail list logo
