Re: [sage-devel] Re: imaginary unit I is smaller than 1

[Daniel Krenn]

On 2017-02-19 17:57, rjf wrote:
> It might be comparing the real parts.  What did you expect?  Perhaps
> Error "<" requires that both operands be members of the same ordered
> field  ??
> Or perhaps just
> False

I, for sure, did not expect "True".


-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] imaginary unit I is smaller than 1

[Daniel Krenn]

On 2017-02-19 12:56, Daniel Krenn wrote:
> I am surprised by
>   sage: bool(I < 1)
>   True

Just to be clear, we are talking about comparison in number fields:

sage: i = I.pyobject()
sage: R = i.parent()
sage: R
Number Field in I with defining polynomial x^2 + 1
sage: i < R(1)
True




-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] patchbot error: HTTP Error 413: Request Entity Too Large

[Thierry]

Hi,

On Mon, Feb 20, 2017 at 08:32:18AM +0100, Jeroen Demeyer wrote:
> On 2017-01-26 10:18, Daniel Krenn wrote:
> >Starting a patchbot results in the error below. Any ideas?
> 
> This issue makes it *impossible* for me to run a patchbot.
> 
> If anybody is able to fix this, please do so.

What happens if you compile Sage before running the patchbot ?

Ciao,
Thierry


> 
> -- 
> 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 sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] imaginary unit I is smaller than 1

[Jeroen Demeyer]

On 2017-02-19 18:01, William Stein wrote:

We generally made everything comparable -- NOT mathematically -- in
Sage, so e.g., one could meaningful and in a well defined way sort the
list of eigenvalues of a matrix, etc., etc.


This thread is about *symbolic* inequalities, which is a different issue.

--
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] patchbot error: HTTP Error 413: Request Entity Too Large

[Jeroen Demeyer]

On 2017-01-26 10:18, Daniel Krenn wrote:

Starting a patchbot results in the error below. Any ideas?


This issue makes it *impossible* for me to run a patchbot.

If anybody is able to fix this, please do so.

--
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: imaginary unit I is smaller than 1

[Ralf Stephan]

Certainly the design of bool(rel) (where rel compares symbolics) can
be improved, including the interface to Maxima with all its switches,
but this specific case is better solved by moving I out of SR:

https://trac.sagemath.org/ticket/18036

Regards,

On Sunday, February 19, 2017 at 12:56:49 PM UTC+1, Daniel Krenn wrote:
>
> Dear all, 
>
> I am surprised by 
>   sage: bool(I < 1) 
>   True 
>
> Best Daniel 
>

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Doctests broken in ticket #20729

[Michael Orlitzky]

On 02/14/2017 10:32 AM, Michael Orlitzky wrote:
> On 02/14/2017 10:19 AM, Erik Bray wrote:
>>
>> Add explicit imports to the test, for example:
>>
>> ...
> 
> Same error: name 'foo' is not defined
> 

If no one has any idea, I would personally prefer it the next release
didn't break every doctest I've ever written.

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: imaginary unit I is smaller than 1

[rjf]

There are a whole bunch of issues raised in the context of   bool(x>0) and 
some mention of what
Maxima does, in that thread from 4 years ago.

But the description of what Maxima* actually does* was essentially missing 
from the discussion.

As is often the case when several different conflicting opinions emerged in 
the design community
for Macsyma/ Maxima , a flag is available to choose a design

Thus
is (a>0)returns unknown.

prederror:true;
is(a>0)   produces an error  "unable to evaluate predicate a>0"


There are  probably other options that have to do with domain:real or 
domain:complex,
and assumptions on individual names.  It is also possible for the system to
return an unevaluated conditional as

if (a>=0 then 1 else 2
  returns unevaluated.   (though  is (a>0)   returns unknown  )

[note difference between is()   and if. ]

I suppose (but have not observed this) that the unevaluated 'if' could be 
simplified. e.g.

if (a^2=a) then 1 else 2 might be simplified to

if  (a=1)or(a=0) then 1 else 2

Now if you wanted to have a program that evaluated a boolean expression 
where
each value was a canonical True or False, and objected somehow otherwise,
that might be a different functionality, and certainly WAY simpler than 
what 
people seem to expect in a computer algebra system.

You could also have a 3 way branching if:   yes/no/unknown.  if a then be 
else c otherwise d.

Perhaps related,

Note also that for IEEE standard floats with  NaNs  (Not a numbers), of 
which there
are a huge number ..all comparisons return false.  That
is for N a NaN and X a float,  all these are false:
N>x
N
> In my opinion not this only particular case but the current bool() design 
> in sage is a tremendous failure.
> This was already discussed on sage-devel several times. 
>
> Here is one of that threads:
> https://groups.google.com/d/msg/sage-devel/vNxnHSeRBW4/UkaBOPGYT0QJ
>
> Jakob
>
> Am Sonntag, 19. Februar 2017 12:56:49 UTC+1 schrieb Daniel Krenn:
>>
>> Dear all, 
>>
>> I am surprised by 
>>   sage: bool(I < 1) 
>>   True 
>>
>> Best Daniel 
>>
>

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Database_gap broken ?

[Dima Pasechnik]

there could also (potentially) be old (lib)GAP workspace files in
~/.sage/gap/
you might want to remove them
(they are automatically regenerated, but it goes wrong in some obscure 
corner cases...)

On Sunday, February 19, 2017 at 10:29:42 PM UTC, Dima Pasechnik wrote:
>
> no clever idea. Can it be that your branch is screwed up somehow?
>
> You can check that the sage 7.6.beta4 branch works with database_gap 
> installed (it does for me, on more than one host,
> and I presume for other people anb bots too),
> really make sure that you're on the correct branch, 
> then bisect your extra commits on top of it to find the one that causes 
> this havoc...
>
>
>
>
>
> On Sunday, February 19, 2017 at 7:42:57 PM UTC, Emmanuel Charpentier wrote:
>>
>>
>>
>> Le dimanche 19 février 2017 20:34:57 UTC+1, Emmanuel Charpentier a écrit :
>>>
>>>
>>>
>>> Le dimanche 19 février 2017 19:54:06 UTC+1, Dima Pasechnik a écrit :



 On Sunday, February 19, 2017 at 6:42:07 PM UTC, Emmanuel Charpentier 
 wrote:
>
> That log is attached to the first message of this thread. BTW, it is 
> suspiciously short...
>

 looks good to me.
  

>
> Should I try to force a reinstallation ?
>
  
>>>

 well, I guess, yes, followed by "make build" just in case...

>>>
>>> Runninfg. Stay tuned. 
>>>
>>
>> Logs attached.
>>
>> Next suggestion ?
>>
>> HTH,
>>
>> --
>> Emmanuel Charpentier
>>  
>>
>>>
 It would also be good to see the output of

 sage --gap

 (there should be 
  Components: trans 1.0, prim 2.1, small* 1.0, id* 1.0
 there, in case database_gap was installed OK)

>>>
>>> It does : 
>>> charpent@asus16-ec:~$ sage -gap
>>>  ┌───┐   GAP 4.8.6, 12-Nov-2016, build of 2017-02-19 01:09:54 (CET)
>>>  │  GAP  │   http://www.gap-system.org
>>>  └───┘   Architecture: x86_64-pc-linux-gnu-gcc-default64
>>>  Libs used:  gmp, readline
>>>  Loading the library and packages ...
>>>  Components: trans 1.0, prim 2.1, small* 1.0, id* 1.0
>>>  Packages:   GAPDoc 1.5.1
>>>  Try '??help' for help. See also '?copyright', '?cite' and '?authors'
>>> gap> 
>>>
>>> HTH,
>>>
>>> --
>>> Emmanuel Charpentier
>>>  
>>>

  

>
> --
> Emmanuel Charpentier
>
> Le dimanche 19 février 2017 19:37:08 UTC+1, Dima Pasechnik a écrit :
>>
>> Your log contains a lot of stuff like
>>
>> TypeError: unsupported operand type(s) for +: 'NoneType' and 'int'
>> 
>> verbose 0 (2059: permgroup_named.py, cardinality) Warning: 
>> TransitiveGroups requires the GAP database package. Please install it 
>> with 
>> ``sage -i database_gap``.
>>
>> That is, you failed to install the package(s) in question...
>> Anything interesting in logs/pkgs/database_gap-4.8.6.log ?
>>
>>
>> On Sunday, February 19, 2017 at 11:37:27 AM UTC, Emmanuel Charpentier 
>> wrote:
>>>
>>> I noticed that installing database_gap gives a *lot* of new doctest 
>>> failures, not all of them reproducible.
>>>
>>> I tested Sage 7.6.beta4 + the patches giving us R 3.3.2 (see this 
>>> , 
>>> by the way...), to which I added got2tex, giagpy_sage and fricas. This 
>>> passes ptestlong with the only (well-known) reproducible error :
>>> charpent@asus16-ec:/usr/local/sage-7$ sage -t --long --warn-long 
>>> 106.9 src/sage/rings/polynomial/multi_polynomial_ideal.py 
>>> Running doctests with ID 2017-02-19-12-15-01-f918671b.
>>> Git branch: checkR
>>> Using --optional=database_gap,giacpy_sage,mpir,python2,sage
>>> Doctesting 1 file.
>>> sage -t --long --warn-long 106.9 
>>> src/sage/rings/polynomial/multi_polynomial_ideal.py
>>>
>>> **
>>> File "src/sage/rings/polynomial/multi_polynomial_ideal.py", line 
>>> 3533, in 
>>> sage.rings.polynomial.multi_polynomial_ideal.NCPolynomialIdeal.groebner_basis
>>> Failed example:
>>> 
>>> ideal(J.transformed_basis()).change_ring(P).interreduced_basis()  # 
>>> optional - giacpy_sage
>>> Expected:
>>> [a - 60*c^3 + 158/7*c^2 + 8/7*c - 1, b + 30*c^3 - 79/7*c^2 + 
>>> 3/7*c, c^4 - 10/21*c^3 + 1/84*c^2 + 1/84*c]
>>> Got:
>>> [7*a - 420*c^3 + 158*c^2 + 8*c - 7, 7*b + 210*c^3 - 79*c^2 + 
>>> 3*c, 84*c^4 - 40*c^3 + c^2 + c]
>>>
>>> **
>>> 1 item had failures:
>>>1 of  67 in 
>>> sage.rings.polynomial.multi_polynomial_ideal.NCPolynomialIdeal.groebner_basis
>>> [727 tests, 1 failure, 9.06 s]
>>>
>>> --
>>> sage -t --long --warn-long 106.9 
>>> 

[sage-devel] Re: Database_gap broken ?

[Dima Pasechnik]

no clever idea. Can it be that your branch is screwed up somehow?

You can check that the sage 7.6.beta4 branch works with database_gap 
installed (it does for me, on more than one host,
and I presume for other people anb bots too),
really make sure that you're on the correct branch, 
then bisect your extra commits on top of it to find the one that causes 
this havoc...





On Sunday, February 19, 2017 at 7:42:57 PM UTC, Emmanuel Charpentier wrote:
>
>
>
> Le dimanche 19 février 2017 20:34:57 UTC+1, Emmanuel Charpentier a écrit :
>>
>>
>>
>> Le dimanche 19 février 2017 19:54:06 UTC+1, Dima Pasechnik a écrit :
>>>
>>>
>>>
>>> On Sunday, February 19, 2017 at 6:42:07 PM UTC, Emmanuel Charpentier 
>>> wrote:

 That log is attached to the first message of this thread. BTW, it is 
 suspiciously short...

>>>
>>> looks good to me.
>>>  
>>>

 Should I try to force a reinstallation ?

>>>  
>>
>>>
>>> well, I guess, yes, followed by "make build" just in case...
>>>
>>
>> Runninfg. Stay tuned. 
>>
>
> Logs attached.
>
> Next suggestion ?
>
> HTH,
>
> --
> Emmanuel Charpentier
>  
>
>>
>>> It would also be good to see the output of
>>>
>>> sage --gap
>>>
>>> (there should be 
>>>  Components: trans 1.0, prim 2.1, small* 1.0, id* 1.0
>>> there, in case database_gap was installed OK)
>>>
>>
>> It does : 
>> charpent@asus16-ec:~$ sage -gap
>>  ┌───┐   GAP 4.8.6, 12-Nov-2016, build of 2017-02-19 01:09:54 (CET)
>>  │  GAP  │   http://www.gap-system.org
>>  └───┘   Architecture: x86_64-pc-linux-gnu-gcc-default64
>>  Libs used:  gmp, readline
>>  Loading the library and packages ...
>>  Components: trans 1.0, prim 2.1, small* 1.0, id* 1.0
>>  Packages:   GAPDoc 1.5.1
>>  Try '??help' for help. See also '?copyright', '?cite' and '?authors'
>> gap> 
>>
>> HTH,
>>
>> --
>> Emmanuel Charpentier
>>  
>>
>>>
>>>  
>>>

 --
 Emmanuel Charpentier

 Le dimanche 19 février 2017 19:37:08 UTC+1, Dima Pasechnik a écrit :
>
> Your log contains a lot of stuff like
>
> TypeError: unsupported operand type(s) for +: 'NoneType' and 'int'
> 
> verbose 0 (2059: permgroup_named.py, cardinality) Warning: 
> TransitiveGroups requires the GAP database package. Please install it 
> with 
> ``sage -i database_gap``.
>
> That is, you failed to install the package(s) in question...
> Anything interesting in logs/pkgs/database_gap-4.8.6.log ?
>
>
> On Sunday, February 19, 2017 at 11:37:27 AM UTC, Emmanuel Charpentier 
> wrote:
>>
>> I noticed that installing database_gap gives a *lot* of new doctest 
>> failures, not all of them reproducible.
>>
>> I tested Sage 7.6.beta4 + the patches giving us R 3.3.2 (see this 
>> , 
>> by the way...), to which I added got2tex, giagpy_sage and fricas. This 
>> passes ptestlong with the only (well-known) reproducible error :
>> charpent@asus16-ec:/usr/local/sage-7$ sage -t --long --warn-long 
>> 106.9 src/sage/rings/polynomial/multi_polynomial_ideal.py 
>> Running doctests with ID 2017-02-19-12-15-01-f918671b.
>> Git branch: checkR
>> Using --optional=database_gap,giacpy_sage,mpir,python2,sage
>> Doctesting 1 file.
>> sage -t --long --warn-long 106.9 
>> src/sage/rings/polynomial/multi_polynomial_ideal.py
>> **
>> File "src/sage/rings/polynomial/multi_polynomial_ideal.py", line 
>> 3533, in 
>> sage.rings.polynomial.multi_polynomial_ideal.NCPolynomialIdeal.groebner_basis
>> Failed example:
>> ideal(J.transformed_basis()).change_ring(P).interreduced_basis()  
>> # optional - giacpy_sage
>> Expected:
>> [a - 60*c^3 + 158/7*c^2 + 8/7*c - 1, b + 30*c^3 - 79/7*c^2 + 
>> 3/7*c, c^4 - 10/21*c^3 + 1/84*c^2 + 1/84*c]
>> Got:
>> [7*a - 420*c^3 + 158*c^2 + 8*c - 7, 7*b + 210*c^3 - 79*c^2 + 3*c, 
>> 84*c^4 - 40*c^3 + c^2 + c]
>> **
>> 1 item had failures:
>>1 of  67 in 
>> sage.rings.polynomial.multi_polynomial_ideal.NCPolynomialIdeal.groebner_basis
>> [727 tests, 1 failure, 9.06 s]
>> --
>> sage -t --long --warn-long 106.9 
>> src/sage/rings/polynomial/multi_polynomial_ideal.py  # 1 doctest failed
>> --
>> Total time for all tests: 9.2 seconds
>> cpu time: 9.7 seconds
>> cumulative wall time: 9.1 seconds
>>
>> Adding database_gap to the mix gave me a slew or new errors :
>> --
>> sage -t --long --warn-long 112.2 
>> 

[sage-devel] Re: Database_gap broken ?

[Emmanuel Charpentier]

Le dimanche 19 février 2017 20:34:57 UTC+1, Emmanuel Charpentier a écrit :
>
>
>
> Le dimanche 19 février 2017 19:54:06 UTC+1, Dima Pasechnik a écrit :
>>
>>
>>
>> On Sunday, February 19, 2017 at 6:42:07 PM UTC, Emmanuel Charpentier 
>> wrote:
>>>
>>> That log is attached to the first message of this thread. BTW, it is 
>>> suspiciously short...
>>>
>>
>> looks good to me.
>>  
>>
>>>
>>> Should I try to force a reinstallation ?
>>>
>>  
>
>>
>> well, I guess, yes, followed by "make build" just in case...
>>
>
> Runninfg. Stay tuned. 
>

Logs attached.

Next suggestion ?

HTH,

--
Emmanuel Charpentier
 

>
>> It would also be good to see the output of
>>
>> sage --gap
>>
>> (there should be 
>>  Components: trans 1.0, prim 2.1, small* 1.0, id* 1.0
>> there, in case database_gap was installed OK)
>>
>
> It does : 
> charpent@asus16-ec:~$ sage -gap
>  ┌───┐   GAP 4.8.6, 12-Nov-2016, build of 2017-02-19 01:09:54 (CET)
>  │  GAP  │   http://www.gap-system.org
>  └───┘   Architecture: x86_64-pc-linux-gnu-gcc-default64
>  Libs used:  gmp, readline
>  Loading the library and packages ...
>  Components: trans 1.0, prim 2.1, small* 1.0, id* 1.0
>  Packages:   GAPDoc 1.5.1
>  Try '??help' for help. See also '?copyright', '?cite' and '?authors'
> gap> 
>
> HTH,
>
> --
> Emmanuel Charpentier
>  
>
>>
>>  
>>
>>>
>>> --
>>> Emmanuel Charpentier
>>>
>>> Le dimanche 19 février 2017 19:37:08 UTC+1, Dima Pasechnik a écrit :

 Your log contains a lot of stuff like

 TypeError: unsupported operand type(s) for +: 'NoneType' and 'int'
 
 verbose 0 (2059: permgroup_named.py, cardinality) Warning: 
 TransitiveGroups requires the GAP database package. Please install it with 
 ``sage -i database_gap``.

 That is, you failed to install the package(s) in question...
 Anything interesting in logs/pkgs/database_gap-4.8.6.log ?


 On Sunday, February 19, 2017 at 11:37:27 AM UTC, Emmanuel Charpentier 
 wrote:
>
> I noticed that installing database_gap gives a *lot* of new doctest 
> failures, not all of them reproducible.
>
> I tested Sage 7.6.beta4 + the patches giving us R 3.3.2 (see this 
> , 
> by the way...), to which I added got2tex, giagpy_sage and fricas. This 
> passes ptestlong with the only (well-known) reproducible error :
> charpent@asus16-ec:/usr/local/sage-7$ sage -t --long --warn-long 106.9 
> src/sage/rings/polynomial/multi_polynomial_ideal.py 
> Running doctests with ID 2017-02-19-12-15-01-f918671b.
> Git branch: checkR
> Using --optional=database_gap,giacpy_sage,mpir,python2,sage
> Doctesting 1 file.
> sage -t --long --warn-long 106.9 
> src/sage/rings/polynomial/multi_polynomial_ideal.py
> **
> File "src/sage/rings/polynomial/multi_polynomial_ideal.py", line 3533, 
> in 
> sage.rings.polynomial.multi_polynomial_ideal.NCPolynomialIdeal.groebner_basis
> Failed example:
> ideal(J.transformed_basis()).change_ring(P).interreduced_basis()  
> # optional - giacpy_sage
> Expected:
> [a - 60*c^3 + 158/7*c^2 + 8/7*c - 1, b + 30*c^3 - 79/7*c^2 + 
> 3/7*c, c^4 - 10/21*c^3 + 1/84*c^2 + 1/84*c]
> Got:
> [7*a - 420*c^3 + 158*c^2 + 8*c - 7, 7*b + 210*c^3 - 79*c^2 + 3*c, 
> 84*c^4 - 40*c^3 + c^2 + c]
> **
> 1 item had failures:
>1 of  67 in 
> sage.rings.polynomial.multi_polynomial_ideal.NCPolynomialIdeal.groebner_basis
> [727 tests, 1 failure, 9.06 s]
> --
> sage -t --long --warn-long 106.9 
> src/sage/rings/polynomial/multi_polynomial_ideal.py  # 1 doctest failed
> --
> Total time for all tests: 9.2 seconds
> cpu time: 9.7 seconds
> cumulative wall time: 9.1 seconds
>
> Adding database_gap to the mix gave me a slew or new errors :
> --
> sage -t --long --warn-long 112.2 
> src/sage/rings/number_field/number_field.py  # 3 doctests failed
> sage -t --long --warn-long 112.2 
> src/sage/groups/perm_gps/permgroup.py  # 11 doctests failed
> sage -t --long --warn-long 112.2 
> src/sage/groups/perm_gps/permgroup_named.py  # 52 doctests failed
> sage -t --long --warn-long 112.2 
> src/sage/rings/polynomial/multi_polynomial_ideal.py  # 1 doctest failed
> sage -t --long --warn-long 112.2 
> src/sage/homology/simplicial_complex.py  # 1 doctest failed
> sage -t --long --warn-long 112.2 src/sage/groups/generic.py  # 5 
> doctests failed
> sage -t --long 

[sage-devel] Re: Database_gap broken ?

[Emmanuel Charpentier]

Le dimanche 19 février 2017 19:54:06 UTC+1, Dima Pasechnik a écrit :
>
>
>
> On Sunday, February 19, 2017 at 6:42:07 PM UTC, Emmanuel Charpentier wrote:
>>
>> That log is attached to the first message of this thread. BTW, it is 
>> suspiciously short...
>>
>
> looks good to me.
>  
>
>>
>> Should I try to force a reinstallation ?
>>
>  

>
> well, I guess, yes, followed by "make build" just in case...
>

Runninfg. Stay tuned. 

>
> It would also be good to see the output of
>
> sage --gap
>
> (there should be 
>  Components: trans 1.0, prim 2.1, small* 1.0, id* 1.0
> there, in case database_gap was installed OK)
>

It does : 
charpent@asus16-ec:~$ sage -gap
 ┌───┐   GAP 4.8.6, 12-Nov-2016, build of 2017-02-19 01:09:54 (CET)
 │  GAP  │   http://www.gap-system.org
 └───┘   Architecture: x86_64-pc-linux-gnu-gcc-default64
 Libs used:  gmp, readline
 Loading the library and packages ...
 Components: trans 1.0, prim 2.1, small* 1.0, id* 1.0
 Packages:   GAPDoc 1.5.1
 Try '??help' for help. See also '?copyright', '?cite' and '?authors'
gap> 

HTH,

--
Emmanuel Charpentier
 

>
>  
>
>>
>> --
>> Emmanuel Charpentier
>>
>> Le dimanche 19 février 2017 19:37:08 UTC+1, Dima Pasechnik a écrit :
>>>
>>> Your log contains a lot of stuff like
>>>
>>> TypeError: unsupported operand type(s) for +: 'NoneType' and 'int'
>>> 
>>> verbose 0 (2059: permgroup_named.py, cardinality) Warning: 
>>> TransitiveGroups requires the GAP database package. Please install it with 
>>> ``sage -i database_gap``.
>>>
>>> That is, you failed to install the package(s) in question...
>>> Anything interesting in logs/pkgs/database_gap-4.8.6.log ?
>>>
>>>
>>> On Sunday, February 19, 2017 at 11:37:27 AM UTC, Emmanuel Charpentier 
>>> wrote:

 I noticed that installing database_gap gives a *lot* of new doctest 
 failures, not all of them reproducible.

 I tested Sage 7.6.beta4 + the patches giving us R 3.3.2 (see this 
 , 
 by the way...), to which I added got2tex, giagpy_sage and fricas. This 
 passes ptestlong with the only (well-known) reproducible error :
 charpent@asus16-ec:/usr/local/sage-7$ sage -t --long --warn-long 106.9 
 src/sage/rings/polynomial/multi_polynomial_ideal.py 
 Running doctests with ID 2017-02-19-12-15-01-f918671b.
 Git branch: checkR
 Using --optional=database_gap,giacpy_sage,mpir,python2,sage
 Doctesting 1 file.
 sage -t --long --warn-long 106.9 
 src/sage/rings/polynomial/multi_polynomial_ideal.py
 **
 File "src/sage/rings/polynomial/multi_polynomial_ideal.py", line 3533, 
 in 
 sage.rings.polynomial.multi_polynomial_ideal.NCPolynomialIdeal.groebner_basis
 Failed example:
 ideal(J.transformed_basis()).change_ring(P).interreduced_basis()  # 
 optional - giacpy_sage
 Expected:
 [a - 60*c^3 + 158/7*c^2 + 8/7*c - 1, b + 30*c^3 - 79/7*c^2 + 3/7*c, 
 c^4 - 10/21*c^3 + 1/84*c^2 + 1/84*c]
 Got:
 [7*a - 420*c^3 + 158*c^2 + 8*c - 7, 7*b + 210*c^3 - 79*c^2 + 3*c, 
 84*c^4 - 40*c^3 + c^2 + c]
 **
 1 item had failures:
1 of  67 in 
 sage.rings.polynomial.multi_polynomial_ideal.NCPolynomialIdeal.groebner_basis
 [727 tests, 1 failure, 9.06 s]
 --
 sage -t --long --warn-long 106.9 
 src/sage/rings/polynomial/multi_polynomial_ideal.py  # 1 doctest failed
 --
 Total time for all tests: 9.2 seconds
 cpu time: 9.7 seconds
 cumulative wall time: 9.1 seconds

 Adding database_gap to the mix gave me a slew or new errors :
 --
 sage -t --long --warn-long 112.2 
 src/sage/rings/number_field/number_field.py  # 3 doctests failed
 sage -t --long --warn-long 112.2 src/sage/groups/perm_gps/permgroup.py  
 # 11 doctests failed
 sage -t --long --warn-long 112.2 
 src/sage/groups/perm_gps/permgroup_named.py  # 52 doctests failed
 sage -t --long --warn-long 112.2 
 src/sage/rings/polynomial/multi_polynomial_ideal.py  # 1 doctest failed
 sage -t --long --warn-long 112.2 
 src/sage/homology/simplicial_complex.py  # 1 doctest failed
 sage -t --long --warn-long 112.2 src/sage/groups/generic.py  # 5 
 doctests failed
 sage -t --long --warn-long 112.2 
 src/sage/combinat/integer_vectors_mod_permgroup.py  # 2 doctests failed
 sage -t --long --warn-long 112.2 
 src/sage/rings/polynomial/polynomial_rational_flint.pyx  # 4 doctests 
 failed
 sage -t --long --warn-long 112.2 
 

[sage-devel] Re: Database_gap broken ?

[Dima Pasechnik]

On Sunday, February 19, 2017 at 6:42:07 PM UTC, Emmanuel Charpentier wrote:
>
> That log is attached to the first message of this thread. BTW, it is 
> suspiciously short...
>

looks good to me.
 

>
> Should I try to force a reinstallation ?
>

well, I guess, yes, followed by "make build" just in case...

It would also be good to see the output of

sage --gap

(there should be 
 Components: trans 1.0, prim 2.1, small* 1.0, id* 1.0
there, in case database_gap was installed OK)

 

>
> --
> Emmanuel Charpentier
>
> Le dimanche 19 février 2017 19:37:08 UTC+1, Dima Pasechnik a écrit :
>>
>> Your log contains a lot of stuff like
>>
>> TypeError: unsupported operand type(s) for +: 'NoneType' and 'int'
>> 
>> verbose 0 (2059: permgroup_named.py, cardinality) Warning: 
>> TransitiveGroups requires the GAP database package. Please install it with 
>> ``sage -i database_gap``.
>>
>> That is, you failed to install the package(s) in question...
>> Anything interesting in logs/pkgs/database_gap-4.8.6.log ?
>>
>>
>> On Sunday, February 19, 2017 at 11:37:27 AM UTC, Emmanuel Charpentier 
>> wrote:
>>>
>>> I noticed that installing database_gap gives a *lot* of new doctest 
>>> failures, not all of them reproducible.
>>>
>>> I tested Sage 7.6.beta4 + the patches giving us R 3.3.2 (see this 
>>> , 
>>> by the way...), to which I added got2tex, giagpy_sage and fricas. This 
>>> passes ptestlong with the only (well-known) reproducible error :
>>> charpent@asus16-ec:/usr/local/sage-7$ sage -t --long --warn-long 106.9 
>>> src/sage/rings/polynomial/multi_polynomial_ideal.py 
>>> Running doctests with ID 2017-02-19-12-15-01-f918671b.
>>> Git branch: checkR
>>> Using --optional=database_gap,giacpy_sage,mpir,python2,sage
>>> Doctesting 1 file.
>>> sage -t --long --warn-long 106.9 
>>> src/sage/rings/polynomial/multi_polynomial_ideal.py
>>> **
>>> File "src/sage/rings/polynomial/multi_polynomial_ideal.py", line 3533, 
>>> in 
>>> sage.rings.polynomial.multi_polynomial_ideal.NCPolynomialIdeal.groebner_basis
>>> Failed example:
>>> ideal(J.transformed_basis()).change_ring(P).interreduced_basis()  # 
>>> optional - giacpy_sage
>>> Expected:
>>> [a - 60*c^3 + 158/7*c^2 + 8/7*c - 1, b + 30*c^3 - 79/7*c^2 + 3/7*c, 
>>> c^4 - 10/21*c^3 + 1/84*c^2 + 1/84*c]
>>> Got:
>>> [7*a - 420*c^3 + 158*c^2 + 8*c - 7, 7*b + 210*c^3 - 79*c^2 + 3*c, 
>>> 84*c^4 - 40*c^3 + c^2 + c]
>>> **
>>> 1 item had failures:
>>>1 of  67 in 
>>> sage.rings.polynomial.multi_polynomial_ideal.NCPolynomialIdeal.groebner_basis
>>> [727 tests, 1 failure, 9.06 s]
>>> --
>>> sage -t --long --warn-long 106.9 
>>> src/sage/rings/polynomial/multi_polynomial_ideal.py  # 1 doctest failed
>>> --
>>> Total time for all tests: 9.2 seconds
>>> cpu time: 9.7 seconds
>>> cumulative wall time: 9.1 seconds
>>>
>>> Adding database_gap to the mix gave me a slew or new errors :
>>> --
>>> sage -t --long --warn-long 112.2 
>>> src/sage/rings/number_field/number_field.py  # 3 doctests failed
>>> sage -t --long --warn-long 112.2 src/sage/groups/perm_gps/permgroup.py  
>>> # 11 doctests failed
>>> sage -t --long --warn-long 112.2 
>>> src/sage/groups/perm_gps/permgroup_named.py  # 52 doctests failed
>>> sage -t --long --warn-long 112.2 
>>> src/sage/rings/polynomial/multi_polynomial_ideal.py  # 1 doctest failed
>>> sage -t --long --warn-long 112.2 
>>> src/sage/homology/simplicial_complex.py  # 1 doctest failed
>>> sage -t --long --warn-long 112.2 src/sage/groups/generic.py  # 5 
>>> doctests failed
>>> sage -t --long --warn-long 112.2 
>>> src/sage/combinat/integer_vectors_mod_permgroup.py  # 2 doctests failed
>>> sage -t --long --warn-long 112.2 
>>> src/sage/rings/polynomial/polynomial_rational_flint.pyx  # 4 doctests failed
>>> sage -t --long --warn-long 112.2 
>>> src/sage/rings/number_field/galois_group.py  # 2 doctests failed
>>> sage -t --long --warn-long 112.2 src/doc/ru/tutorial/interfaces.rst  # 2 
>>> doctests failed
>>> sage -t --long --warn-long 112.2 src/doc/de/tutorial/interfaces.rst  # 2 
>>> doctests failed
>>> sage -t --long --warn-long 112.2 src/sage/combinat/sloane_functions.py  
>>> # 2 doctests failed
>>> sage -t --long --warn-long 112.2 src/doc/pt/tutorial/interfaces.rst  # 2 
>>> doctests failed
>>> sage -t --long --warn-long 112.2 src/doc/ja/tutorial/interfaces.rst  # 2 
>>> doctests failed
>>> sage -t --long --warn-long 112.2 src/doc/en/tutorial/interfaces.rst  # 2 
>>> doctests failed
>>> sage -t --long --warn-long 112.2 src/doc/en/constructions/groups.rst  # 
>>> 

[sage-devel] Re: Database_gap broken ?

[Emmanuel Charpentier]

That log is attached to the first message of this thread. BTW, it is 
suspiciously short...

Should I try to force a reinstallation ?

--
Emmanuel Charpentier

Le dimanche 19 février 2017 19:37:08 UTC+1, Dima Pasechnik a écrit :
>
> Your log contains a lot of stuff like
>
> TypeError: unsupported operand type(s) for +: 'NoneType' and 'int'
> 
> verbose 0 (2059: permgroup_named.py, cardinality) Warning: 
> TransitiveGroups requires the GAP database package. Please install it with 
> ``sage -i database_gap``.
>
> That is, you failed to install the package(s) in question...
> Anything interesting in logs/pkgs/database_gap-4.8.6.log ?
>
>
> On Sunday, February 19, 2017 at 11:37:27 AM UTC, Emmanuel Charpentier 
> wrote:
>>
>> I noticed that installing database_gap gives a *lot* of new doctest 
>> failures, not all of them reproducible.
>>
>> I tested Sage 7.6.beta4 + the patches giving us R 3.3.2 (see this 
>> , 
>> by the way...), to which I added got2tex, giagpy_sage and fricas. This 
>> passes ptestlong with the only (well-known) reproducible error :
>> charpent@asus16-ec:/usr/local/sage-7$ sage -t --long --warn-long 106.9 
>> src/sage/rings/polynomial/multi_polynomial_ideal.py 
>> Running doctests with ID 2017-02-19-12-15-01-f918671b.
>> Git branch: checkR
>> Using --optional=database_gap,giacpy_sage,mpir,python2,sage
>> Doctesting 1 file.
>> sage -t --long --warn-long 106.9 
>> src/sage/rings/polynomial/multi_polynomial_ideal.py
>> **
>> File "src/sage/rings/polynomial/multi_polynomial_ideal.py", line 3533, in 
>> sage.rings.polynomial.multi_polynomial_ideal.NCPolynomialIdeal.groebner_basis
>> Failed example:
>> ideal(J.transformed_basis()).change_ring(P).interreduced_basis()  # 
>> optional - giacpy_sage
>> Expected:
>> [a - 60*c^3 + 158/7*c^2 + 8/7*c - 1, b + 30*c^3 - 79/7*c^2 + 3/7*c, 
>> c^4 - 10/21*c^3 + 1/84*c^2 + 1/84*c]
>> Got:
>> [7*a - 420*c^3 + 158*c^2 + 8*c - 7, 7*b + 210*c^3 - 79*c^2 + 3*c, 
>> 84*c^4 - 40*c^3 + c^2 + c]
>> **
>> 1 item had failures:
>>1 of  67 in 
>> sage.rings.polynomial.multi_polynomial_ideal.NCPolynomialIdeal.groebner_basis
>> [727 tests, 1 failure, 9.06 s]
>> --
>> sage -t --long --warn-long 106.9 
>> src/sage/rings/polynomial/multi_polynomial_ideal.py  # 1 doctest failed
>> --
>> Total time for all tests: 9.2 seconds
>> cpu time: 9.7 seconds
>> cumulative wall time: 9.1 seconds
>>
>> Adding database_gap to the mix gave me a slew or new errors :
>> --
>> sage -t --long --warn-long 112.2 
>> src/sage/rings/number_field/number_field.py  # 3 doctests failed
>> sage -t --long --warn-long 112.2 src/sage/groups/perm_gps/permgroup.py  # 
>> 11 doctests failed
>> sage -t --long --warn-long 112.2 
>> src/sage/groups/perm_gps/permgroup_named.py  # 52 doctests failed
>> sage -t --long --warn-long 112.2 
>> src/sage/rings/polynomial/multi_polynomial_ideal.py  # 1 doctest failed
>> sage -t --long --warn-long 112.2 src/sage/homology/simplicial_complex.py  
>> # 1 doctest failed
>> sage -t --long --warn-long 112.2 src/sage/groups/generic.py  # 5 doctests 
>> failed
>> sage -t --long --warn-long 112.2 
>> src/sage/combinat/integer_vectors_mod_permgroup.py  # 2 doctests failed
>> sage -t --long --warn-long 112.2 
>> src/sage/rings/polynomial/polynomial_rational_flint.pyx  # 4 doctests failed
>> sage -t --long --warn-long 112.2 
>> src/sage/rings/number_field/galois_group.py  # 2 doctests failed
>> sage -t --long --warn-long 112.2 src/doc/ru/tutorial/interfaces.rst  # 2 
>> doctests failed
>> sage -t --long --warn-long 112.2 src/doc/de/tutorial/interfaces.rst  # 2 
>> doctests failed
>> sage -t --long --warn-long 112.2 src/sage/combinat/sloane_functions.py  # 
>> 2 doctests failed
>> sage -t --long --warn-long 112.2 src/doc/pt/tutorial/interfaces.rst  # 2 
>> doctests failed
>> sage -t --long --warn-long 112.2 src/doc/ja/tutorial/interfaces.rst  # 2 
>> doctests failed
>> sage -t --long --warn-long 112.2 src/doc/en/tutorial/interfaces.rst  # 2 
>> doctests failed
>> sage -t --long --warn-long 112.2 src/doc/en/constructions/groups.rst  # 1 
>> doctest failed
>> sage -t --long --warn-long 112.2 src/doc/fr/tutorial/interfaces.rst  # 2 
>> doctests failed
>> sage -t --long --warn-long 112.2 
>> src/sage/categories/finite_permutation_groups.py  # 1 doctest failed
>> sage -t --long --warn-long 112.2 
>> src/sage/matrix/matrix_modn_dense_template.pxi  # Timed out
>> --
>>
>> (collected in the enclosed file errors.in).
>>
>> 

[sage-devel] Re: Database_gap broken ?

[Dima Pasechnik]

Your log contains a lot of stuff like

TypeError: unsupported operand type(s) for +: 'NoneType' and 'int'

verbose 0 (2059: permgroup_named.py, cardinality) Warning: 
TransitiveGroups requires the GAP database package. Please install it with 
``sage -i database_gap``.

That is, you failed to install the package(s) in question...
Anything interesting in logs/pkgs/database_gap-4.8.6.log ?


On Sunday, February 19, 2017 at 11:37:27 AM UTC, Emmanuel Charpentier wrote:
>
> I noticed that installing database_gap gives a *lot* of new doctest 
> failures, not all of them reproducible.
>
> I tested Sage 7.6.beta4 + the patches giving us R 3.3.2 (see this 
> , by 
> the way...), to which I added got2tex, giagpy_sage and fricas. This passes 
> ptestlong with the only (well-known) reproducible error :
> charpent@asus16-ec:/usr/local/sage-7$ sage -t --long --warn-long 106.9 
> src/sage/rings/polynomial/multi_polynomial_ideal.py 
> Running doctests with ID 2017-02-19-12-15-01-f918671b.
> Git branch: checkR
> Using --optional=database_gap,giacpy_sage,mpir,python2,sage
> Doctesting 1 file.
> sage -t --long --warn-long 106.9 
> src/sage/rings/polynomial/multi_polynomial_ideal.py
> **
> File "src/sage/rings/polynomial/multi_polynomial_ideal.py", line 3533, in 
> sage.rings.polynomial.multi_polynomial_ideal.NCPolynomialIdeal.groebner_basis
> Failed example:
> ideal(J.transformed_basis()).change_ring(P).interreduced_basis()  # 
> optional - giacpy_sage
> Expected:
> [a - 60*c^3 + 158/7*c^2 + 8/7*c - 1, b + 30*c^3 - 79/7*c^2 + 3/7*c, 
> c^4 - 10/21*c^3 + 1/84*c^2 + 1/84*c]
> Got:
> [7*a - 420*c^3 + 158*c^2 + 8*c - 7, 7*b + 210*c^3 - 79*c^2 + 3*c, 
> 84*c^4 - 40*c^3 + c^2 + c]
> **
> 1 item had failures:
>1 of  67 in 
> sage.rings.polynomial.multi_polynomial_ideal.NCPolynomialIdeal.groebner_basis
> [727 tests, 1 failure, 9.06 s]
> --
> sage -t --long --warn-long 106.9 
> src/sage/rings/polynomial/multi_polynomial_ideal.py  # 1 doctest failed
> --
> Total time for all tests: 9.2 seconds
> cpu time: 9.7 seconds
> cumulative wall time: 9.1 seconds
>
> Adding database_gap to the mix gave me a slew or new errors :
> --
> sage -t --long --warn-long 112.2 
> src/sage/rings/number_field/number_field.py  # 3 doctests failed
> sage -t --long --warn-long 112.2 src/sage/groups/perm_gps/permgroup.py  # 
> 11 doctests failed
> sage -t --long --warn-long 112.2 
> src/sage/groups/perm_gps/permgroup_named.py  # 52 doctests failed
> sage -t --long --warn-long 112.2 
> src/sage/rings/polynomial/multi_polynomial_ideal.py  # 1 doctest failed
> sage -t --long --warn-long 112.2 src/sage/homology/simplicial_complex.py  
> # 1 doctest failed
> sage -t --long --warn-long 112.2 src/sage/groups/generic.py  # 5 doctests 
> failed
> sage -t --long --warn-long 112.2 
> src/sage/combinat/integer_vectors_mod_permgroup.py  # 2 doctests failed
> sage -t --long --warn-long 112.2 
> src/sage/rings/polynomial/polynomial_rational_flint.pyx  # 4 doctests failed
> sage -t --long --warn-long 112.2 
> src/sage/rings/number_field/galois_group.py  # 2 doctests failed
> sage -t --long --warn-long 112.2 src/doc/ru/tutorial/interfaces.rst  # 2 
> doctests failed
> sage -t --long --warn-long 112.2 src/doc/de/tutorial/interfaces.rst  # 2 
> doctests failed
> sage -t --long --warn-long 112.2 src/sage/combinat/sloane_functions.py  # 
> 2 doctests failed
> sage -t --long --warn-long 112.2 src/doc/pt/tutorial/interfaces.rst  # 2 
> doctests failed
> sage -t --long --warn-long 112.2 src/doc/ja/tutorial/interfaces.rst  # 2 
> doctests failed
> sage -t --long --warn-long 112.2 src/doc/en/tutorial/interfaces.rst  # 2 
> doctests failed
> sage -t --long --warn-long 112.2 src/doc/en/constructions/groups.rst  # 1 
> doctest failed
> sage -t --long --warn-long 112.2 src/doc/fr/tutorial/interfaces.rst  # 2 
> doctests failed
> sage -t --long --warn-long 112.2 
> src/sage/categories/finite_permutation_groups.py  # 1 doctest failed
> sage -t --long --warn-long 112.2 
> src/sage/matrix/matrix_modn_dense_template.pxi  # Timed out
> --
>
> (collected in the enclosed file errors.in).
>
> Re-running them (by the simple expedient of source errors.in > errors.out 
> 2>&1) showed that those errors are not transient (see the enclosed file 
> errors.out).
>
> I also enclose the installation log of database_gap, as well as the 
> ptestlong logs before and after database_gap installation ; all files are 
> gzipped.
>
> I *think* that 

[sage-devel] Re: imaginary unit I is smaller than 1

[Jakob Kroeker]

In my opinion not this only particular case but the current bool() design 
in sage is a tremendous failure.
This was already discussed on sage-devel several times. 

Here is one of that threads:
https://groups.google.com/d/msg/sage-devel/vNxnHSeRBW4/UkaBOPGYT0QJ

Jakob

Am Sonntag, 19. Februar 2017 12:56:49 UTC+1 schrieb Daniel Krenn:
>
> Dear all, 
>
> I am surprised by 
>   sage: bool(I < 1) 
>   True 
>
> Best Daniel 
>

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] imaginary unit I is smaller than 1

[William Stein]

We generally made everything comparable -- NOT mathematically -- in
Sage, so e.g., one could meaningful and in a well defined way sort the
list of eigenvalues of a matrix, etc., etc.

However, I think when we switch to Python3, we'll likely change this
and raise a lot of errors, or so I hear...   And for sorting in a
meaningful way we'll be more explicit.

William

On Sun, Feb 19, 2017 at 3:56 AM, Daniel Krenn  wrote:
> Dear all,
>
> I am surprised by
>   sage: bool(I < 1)
>   True
>
> Best Daniel
>
> --
> 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 sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: imaginary unit I is smaller than 1

[rjf]

It might be comparing the real parts.  What did you expect?  Perhaps
Error "<" requires that both operands be members of the same ordered field 
 ??
Or perhaps just
False


On Sunday, February 19, 2017 at 3:56:49 AM UTC-8, Daniel Krenn wrote:
>
> Dear all, 
>
> I am surprised by 
>   sage: bool(I < 1) 
>   True 
>
> Best Daniel 
>

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Database_gap broken ?

[Emmanuel Charpentier]

Le dimanche 19 février 2017 12:58:40 UTC+1, Emmanuel Charpentier a écrit :
>
> Indeed, I didn't install gap_packages. I'll install it and retest later 
> this afternoon...
>

Alas... It's worse :
--
sage -t --long src/sage/coding/linear_code.py  # 1 doctest failed
sage -t --long src/sage/rings/number_field/number_field.py  # 3 doctests 
failed
sage -t --long src/sage/rings/polynomial/multi_polynomial_ideal.py  # 1 
doctest failed
sage -t --long src/sage/groups/perm_gps/permgroup.py  # 11 doctests failed
sage -t --long src/sage/groups/perm_gps/permgroup_named.py  # 52 doctests 
failed
sage -t --long src/sage/rings/polynomial/polynomial_rational_flint.pyx  # 4 
doctests failed
sage -t --long src/sage/combinat/integer_vectors_mod_permgroup.py  # 2 
doctests failed
sage -t --long src/sage/groups/generic.py  # 5 doctests failed
sage -t --long src/sage/rings/number_field/galois_group.py  # 2 doctests 
failed
sage -t --long src/sage/combinat/sloane_functions.py  # 2 doctests failed
sage -t --long src/doc/de/tutorial/interfaces.rst  # 2 doctests failed
sage -t --long src/doc/ja/tutorial/interfaces.rst  # 2 doctests failed
sage -t --long src/doc/ru/tutorial/interfaces.rst  # 2 doctests failed
sage -t --long src/doc/pt/tutorial/interfaces.rst  # 2 doctests failed
sage -t --long src/doc/fr/tutorial/interfaces.rst  # 2 doctests failed
sage -t --long src/doc/en/tutorial/interfaces.rst  # 2 doctests failed
sage -t --long src/doc/en/constructions/groups.rst  # 1 doctest failed
sage -t --long src/sage/categories/finite_permutation_groups.py  # 1 
doctest failed
--

As before, relevant logs and test reruns attached.

HTH,

--
Emmanuel Charpentier
 

>
> --
> Emmanuel Charpentier
>
>
> Le 19 févr. 2017 12:55, "Dima Pasechnik"  a écrit :
>
>> could it be that you did install database_gap, but no gap_packages?
>> We probably only tested them together...
>>
>> --
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "sage-devel" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/sage-devel/ipGaDf4gu0k/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> sage-devel+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-devel@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-devel.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


errors2.in.gz
Description: Binary data


errors2.out.gz
Description: Binary data


gap_packages-4.8.6.p2.log.gz
Description: Binary data


ptestlong-with-gap_packages.log.gz
Description: Binary data

Re: [sage-devel] Database_gap broken ?

[Emmanuel Charpentier]

Indeed, I didn't install gap_packages. I'll install it and retest later
this afternoon...

--
Emmanuel Charpentier


Le 19 févr. 2017 12:55, "Dima Pasechnik"  a écrit :

> could it be that you did install database_gap, but no gap_packages?
> We probably only tested them together...
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/sage-devel/ipGaDf4gu0k/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] imaginary unit I is smaller than 1

[Daniel Krenn]

Dear all,

I am surprised by
  sage: bool(I < 1)
  True

Best Daniel

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Database_gap broken ?

[Dima Pasechnik]

could it be that you did install database_gap, but no gap_packages?
We probably only tested them together...

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: BGG Sage microbadge

[Andrew]

Ah, so not Bernstein-Gelfand-Gelfand then...


On Sunday, 19 February 2017 13:59:14 UTC+11, kcrisman wrote:
>
> For those who are true board game geeks (of which I know a number on this 
> list):
>
> https://boardgamegeek.com/microbadge/9453
>
> I have no idea who the creator is, but hats off!
>

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.