[sage-devel] Error, Variable: '_rich_repr_' must have a value / new libgap

2018-09-26 Thread Dima Pasechnik
On https://trac.sagemath.org/ticket/22626 (update to GAP 4.10 with unification of libgap and GAP, the current branch is showing signs of life...) I am getting sage: libgap(1) Error, Variable: '_rich_repr_' must have a value Error, Variable: '_ipython_canary_method_should_not_exist_' must have a\

Re: [sage-devel] semantics of ... in doctests

2018-09-26 Thread 'Martin R' via sage-devel
actually, I took an old copy of 8.2.rc0, copied over the current version of findstat.py and all tests pass. so something has changed. Am Mittwoch, 26. September 2018 12:56:51 UTC+2 schrieb Martin R: > > strange, because this line has been there since 2015. > > Am Mittwoch, 26. September 2018

Re: [sage-devel] sage foundation ???

2018-09-26 Thread Dima Pasechnik
On Wed, Sep 26, 2018 at 10:35 AM Jeroen Demeyer wrote: > > On 2018-09-24 18:00, Dima Pasechnik wrote: > > Perhaps the most tricky is 2 (or perhaps not anymore, after out > > infamous CoC discussion fiasco we could agree it makes sense to get > > something in place; we can have a look at > >

Re: [sage-devel] sage foundation ???

2018-09-26 Thread William Stein
On Wed, Sep 26, 2018 at 3:14 AM, Dima Pasechnik wrote: > On Wed, Sep 26, 2018 at 10:35 AM Jeroen Demeyer wrote: >> >> On 2018-09-24 18:00, Dima Pasechnik wrote: >> > Perhaps the most tricky is 2 (or perhaps not anymore, after out >> > infamous CoC discussion fiasco we could agree it makes sense

Re: [sage-devel] semantics of ... in doctests

2018-09-26 Thread Jeroen Demeyer
On 2018-09-26 16:48, 'Martin R' via sage-devel wrote: Indeed, it seems that the test is not actually being run. You mean that it *was* not actually being run, but now it is. I don't know what caused the change, but it's clearly in the good sense since that doctest should be run. -- You

Re: [sage-devel] semantics of ... in doctests

2018-09-26 Thread 'Martin R' via sage-devel
Indeed, it seems that the test is not actually being run. I modified it as follows, and it is still not reported: sage: def f(pi): : print("hi") : return pi.saliances()[0] sage: r = findstat(Permutations, lambda pi: f(pi)); r #

Re: [sage-devel] semantics of ... in doctests

2018-09-26 Thread 'Martin R' via sage-devel
martin@convex63:~/sage-master$ cat VERSION.txt SageMath version 8.3, Release Date: 2018-08-03 martin@convex63:~/sage-master$ ./sage -tp --long --optional=sage,optional,external,internet src/sage/databases/findstat.py too many failed tests, not using stored timings Running doctests with ID

Re: [sage-devel] sage foundation ???

2018-09-26 Thread Erik Bray
On Wed, Sep 26, 2018 at 4:48 PM William Stein wrote: > > On Wed, Sep 26, 2018 at 3:14 AM, Dima Pasechnik wrote: > > On Wed, Sep 26, 2018 at 10:35 AM Jeroen Demeyer wrote: > >> > >> On 2018-09-24 18:00, Dima Pasechnik wrote: > >> > Perhaps the most tricky is 2 (or perhaps not anymore, after out

Re: [sage-devel] sage foundation ???

2018-09-26 Thread Dima Pasechnik
On Wed, 26 Sep 2018, 18:04 Erik Bray, wrote: > On Wed, Sep 26, 2018 at 4:48 PM William Stein wrote: > > > > On Wed, Sep 26, 2018 at 3:14 AM, Dima Pasechnik > wrote: > > > On Wed, Sep 26, 2018 at 10:35 AM Jeroen Demeyer > wrote: > > >> > > >> On 2018-09-24 18:00, Dima Pasechnik wrote: > > >> >

Re: [sage-devel] semantics of ... in doctests

2018-09-26 Thread 'Martin R' via sage-devel
strange, because this line has been there since 2015. Am Mittwoch, 26. September 2018 10:54:17 UTC+2 schrieb Jeroen Demeyer: > > On 2018-09-26 10:10, 'Martin R' via sage-devel wrote: > > In https://trac.sagemath.org/ticket/26348 a doctest is failing, because > > apparently the semantics of

Re: [sage-devel] semantics of ... in doctests

2018-09-26 Thread Erik Bray
There was a recently fixed bug with doctest parsing. Fixing the bug also caused some tests that were affected by that bug to suddenly start failing (rather, because they weren't being run in the first place). I'm not sure if it's relevant to your case or not:

Re: [sage-devel] semantics of ... in doctests

2018-09-26 Thread Jeroen Demeyer
On 2018-09-26 13:03, 'Martin R' via sage-devel wrote: and all tests pass. Which command are you using to run the tests? Something might have changed there. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and

[sage-devel] semantics of ... in doctests

2018-09-26 Thread 'Martin R' via sage-devel
In https://trac.sagemath.org/ticket/26348 a doctest is failing, because apparently the semantics of "..." has changed. Here is the test: ## sage: r = findstat(Permutations, lambda pi: pi.saliances()[0]); r # optional -- internet, random ... ...

Re: [sage-devel] sage foundation ???

2018-09-26 Thread Erik Bray
On Mon, Sep 24, 2018 at 8:15 PM William Stein wrote: > > On Mon, Sep 24, 2018 at 9:35 AM, Erik Bray wrote: > > 5) also might be harder than you think--or at least, even if we can > > come up with an uncontroversial list of names, it's a discussion that > > invites questions about project

Re: [sage-devel] semantics of ... in doctests

2018-09-26 Thread Jeroen Demeyer
On 2018-09-26 10:10, 'Martin R' via sage-devel wrote: In https://trac.sagemath.org/ticket/26348 a doctest is failing, because apparently the semantics of "..." has changed. I don't think that anything has changed here. As far as I know, "..." at the start of a line after a "sage:" line has

Re: [sage-devel] semantics of ... in doctests

2018-09-26 Thread Erik Bray
On Wed, Sep 26, 2018 at 10:54 AM Jeroen Demeyer wrote: > > On 2018-09-26 10:10, 'Martin R' via sage-devel wrote: > > In https://trac.sagemath.org/ticket/26348 a doctest is failing, because > > apparently the semantics of "..." has changed. > > I don't think that anything has changed here. As far

Re: [sage-devel] sage foundation ???

2018-09-26 Thread Jeroen Demeyer
On 2018-09-24 18:00, Dima Pasechnik wrote: Perhaps the most tricky is 2 (or perhaps not anymore, after out infamous CoC discussion fiasco we could agree it makes sense to get something in place; we can have a look at https://numfocus.org/code-of-conduct and see if we can just agree to this)