[sage-release] Re: Sage 8.0.beta11 released

2017-06-18 Thread Eric Gourgoulhon
Le samedi 17 juin 2017 23:09:52 UTC+2, Sébastien Labbé a écrit :

>
> It is better to set colors Linux in the file
> profile_default/ipython_config.py
> see
> https://ask.sagemath.org/question/10060/sage-terminal-colors/
> (not the first answer:)
>

Thanks for the tip Sébastien! It works well.

Eric. 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-release] Re: Sage 8.0.beta11 released

2017-06-17 Thread Volker Braun
Needs review...

On Saturday, June 17, 2017 at 7:37:04 PM UTC+2, Daniel Krenn wrote:
>
> On 2017-06-17 15:31, Eric Gourgoulhon wrote: 
> > Le vendredi 16 juin 2017 18:44:29 UTC+2, Volker Braun a écrit : 
> > 
> > It looks like something in your Sage or IPython startup files 
> > unconditionally enables ansi color. 
> > 
> > 
> > Thanks  Volker! This is indeed the case: I've recently added the line 
> > %colors Linux 
> > to the file ~/.sage/init.sage 
> > Removing it fixes the problem. 
>
> This is already 
>   https://trac.sagemath.org/ticket/20270 
> My impression is that fixing this as suggested on the ticket is not too 
> hard, but unfortunately, I have no glue and this part of Sage to fix it. 
>
> Can anyone fix this (soon)? (I am annoyed since 7.6.beta2 (first time I 
> recognized this) 
>
> Best regards 
>
> Daniel 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


[sage-release] Re: Sage 8.0.beta11 released

2017-06-17 Thread Sébastien Labbé


> Thanks  Volker! This is indeed the case: I've recently added the line 
> %colors Linux
> to the file ~/.sage/init.sage
> Removing it fixes the problem.
>

It is better to set colors Linux in the file
profile_default/ipython_config.py
see
https://ask.sagemath.org/question/10060/sage-terminal-colors/
(not the first answer:)

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-release] Re: Sage 8.0.beta11 released

2017-06-17 Thread Daniel Krenn
On 2017-06-17 15:31, Eric Gourgoulhon wrote:
> Le vendredi 16 juin 2017 18:44:29 UTC+2, Volker Braun a écrit :
> 
> It looks like something in your Sage or IPython startup files
> unconditionally enables ansi color. 
> 
> 
> Thanks  Volker! This is indeed the case: I've recently added the line
> %colors Linux
> to the file ~/.sage/init.sage
> Removing it fixes the problem.

This is already
  https://trac.sagemath.org/ticket/20270
My impression is that fixing this as suggested on the ticket is not too
hard, but unfortunately, I have no glue and this part of Sage to fix it.

Can anyone fix this (soon)? (I am annoyed since 7.6.beta2 (first time I
recognized this)

Best regards

Daniel

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


[sage-release] Re: Sage 8.0.beta11 released

2017-06-17 Thread Emmanuel Charpentier
On Debian testing, running on Core i7 + 18 GB RAM, I get two transient 
failures :

--
sage -t --long src/sage/homology/simplicial_complex.py  # 1 doctest failed
sage -t --long src/sage/interfaces/giac.py  # Timed out
--

Both pass when ran stansalone.

HTH,

--
Emmanuel Charpentier

Le jeudi 15 juin 2017 19:52:23 UTC+2, Volker Braun a écrit :
>
> As always, you can get the latest beta version from the "develop" git 
> branch. Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html
>
> 61fa91f Updated SageMath version to 8.0.beta11
> 7c4805d Trac #23225: fix tuning of gf2x
> b669ff9 Trac #23206: partition_algebra.py: use normal functions instead of 
> functools.partial
> b7debae Trac #23077: Fix complex handling of libs/pynac/py_float()
> e66e7e5 Trac #23057: libfplll does not pass self-tests on 32bit systems
> 2bf71fe Trac #22986: Refactor SBox code (move from crypto.mq to crypto)
> 7be374f Trac #23053: database_gap doesn't work after installing it
> b4e482e Trac #23038: Cython testsuite failure
> 47dfe32 Trac #23165: valence polynomial for posets
> 07aedaf Trac #23223: py3: some changes about cmp in groups and combinat
> fb869a9 Trac #23199: missing sig_on/off in symbolic arithmetics
> 87e81e1 Trac #23163: py3: some care for cmp of power and Laurent series
> 461478a Trac #22853: Update Coxeter Group documentation
> c43f892 Trac #23164: cache Polynomial.is_irreducible()
> 1748669 Trac #23151: more typos in internal links syntax
> a03012d Trac #23118: Faster is_pseudocomplemented()
> 1dec1e3 Trac #23113: a few typos in internal links syntax
> 7a4d390 Trac #23086: cyclegraph for Projective Morphisms
> 2f34888 Trac #23081: Matchings in multigraphs
> e68c87e Trac #23020: Do not require coefficient's __nonzero__ to be 
> implemented for polynomial printing
> 8a4a763 Trac #16576: Improve monic_integral_model() for function fields
> f2088cf Trac #16575: change_variable_name() for function fields
> e4a28d6 Trac #16563: simple model for function fields
> 83e1cca Trac #23221: Coercion from floating point unramified rings to 
> their fraction fields
> 6d341bf Trac #23219: Make cryptominisat an optional package
> 1136114 Trac #23167: Coercions between Function Fields
> b76c5a3 Trac #23145: Interval and ball field elements conversion to Python 
> float/complex
> b4407a7 Trac #23127: Stop using cysignals .pxi files (part 6)
> 9a6a6c0 Trac #22818: Interface cryptominisat 5
> 70a605e Trac #22817: Package cryptominisat 5
> b2adb1c Trac #21433: pushout and unique parent for finite fields
> ddb9dac Trac #23011: ECL sometimes doesn't handle signals in a timely 
> manner
> 25fca88 Trac #22989: Doctest: Remaining issues with symbolic product
> 1bdd577 Trac #22913: Reynolds Operator
> 56188e5 Trac #22560: Replace deprecated sphinx.ext.pngmath
> c1f07ea Trac #20778: Add certificate option to has_line_minor
> 163b84e Trac #19457: Generator for full binary trees
> 74c2f99 Trac #23216: Matrix of a module morphism who domain is 0 is always 
> 0x0
> f92e205 Trac #23215: Missing except in symbolic power
> 8266e46 Trac #23184: Use the right category for DefaultConvertMaps, rather 
> than SetsWithPartialMaps
> 39d5735 Trac #23205: Do not require surjectivity to be implemented for 
> composite injectivity
> 90df803 Trac #23201: Hecke triangle group cusp form base ring
> de53ee5 Trac #23200: Graphics3dGroup.texture_set does not handle when the 
> group is empty
> 22a1661 Trac #23183: Change LaurentSeriesRing_generic to be a 
> UniqueRepresentation
> 664fc1e Trac #23181: Incorrect implementation of Hasse-Witt matrix for 
> Hyperelliptic Curves
> e0dfc3c Trac #23180: Upgrading experimental GAP3 package to version 01may17
> 089131d Trac #23178: Do not generate local/share/sage/doc/output symlink
> 05d24d6 Trac #23176: Stop using cysignals .pxi files (part 7)
> 8d191b6 Trac #23152: Add 'is_separable' to function field class
> ffc8eff Updated SageMath version to 8.0.beta10
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-release] Re: Sage 8.0.beta11 released

2017-06-17 Thread William Stein
On Sat, Jun 17, 2017 at 7:01 AM Volker Braun  wrote:

> On Saturday, June 17, 2017 at 3:31:51 PM UTC+2, Eric Gourgoulhon wrote:
>>
>> Actually, without the above line, the colors are weird when running Sage
>> console in a terminal: the sage prompt and all numbers in input lines are
>> displayed in dark blue over a black background, which is barely readable.
>> By the way, this may disturb newcomers to Sage (at least from Ubuntu).
>> Could the default colors be changed?
>>
>
>  Ergonomic research showed time and again that dark text on light
> background is more readable. I'm fine with changing defaults but they need
> to work on light backgrounds...
>

One should support both.   Which is better depends on the person, their
device, and ambient lighting...





-- 
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>
-- 
-- William Stein

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


[sage-release] Re: Sage 8.0.beta11 released

2017-06-17 Thread Eric Gourgoulhon
Le vendredi 16 juin 2017 18:44:29 UTC+2, Volker Braun a écrit :
>
> It looks like something in your Sage or IPython startup files 
> unconditionally enables ansi color. 
>
>
Thanks  Volker! This is indeed the case: I've recently added the line 
%colors Linux
to the file ~/.sage/init.sage
Removing it fixes the problem.

Actually, without the above line, the colors are weird when running Sage 
console in a terminal: the sage prompt and all numbers in input lines are 
displayed in dark blue over a black background, which is barely readable.
By the way, this may disturb newcomers to Sage (at least from Ubuntu). 
Could the default colors be changed?

Best regards,

Eric.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


[sage-release] Re: Sage 8.0.beta11 released

2017-06-16 Thread Eric Gourgoulhon
On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git clone + 
pull develop, parallel (-j16) build OK, but make ptestlong failed with the 
same files as for 8.0.beta10:
sage -t --long --warn-long 51.3 src/sage/interfaces/expect.py  # 1 doctest 
failed
sage -t --long --warn-long 51.3 src/sage/repl/interpreter.py  # 3 doctests 
failed
sage -t --long --warn-long 51.3 src/sage/repl/interface_magic.py  # 3 
doctests failed
sage -t --long --warn-long 51.3 src/sage/repl/ipython_tests.py  # 4 
doctests failed
See https://groups.google.com/d/msg/sage-release/Apd_Q8gc5F8/NgZBLSsuAgAJ 
for details

Apparently, Sébastien, who is using Ubuntu 16.04 as well, does not have 
this problem. Any hint?

Eric. 


-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


[sage-release] Re: Sage 8.0.beta11 released

2017-06-16 Thread Sébastien Labbé
On osx 10.10, make ptestlong gives: All test passed!

On Ubuntu 16.04, make ptestlong gives
--
sage -t --long --warn-long 61.1 src/sage/sat/boolean_polynomials.py  # 1 
doctest failed
--

The error is:

sage -t --long --warn-long 61.1 src/sage/sat/boolean_polynomials.py
**
File "src/sage/sat/boolean_polynomials.py", line 89, in 
sage.sat.boolean_polynomials.solve
Failed example:
s = solve_sat(F, s_verbosity=1, c_max_vars_sparse=4, 
c_cutting_number=8) # optional - cryptominisat
Expected:
c --> ...
...
Got:
c [consolidate] T: 0.00
c Found matrixes: 0 T: 0.00 T-out: N
**
1 item had failures:
   1 of  22 in sage.sat.boolean_polynomials.solve
[27 tests, 1 failure, 0.79 s]


I can't reproduce it.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.