Re: [sage-release] Re: Sage 6.6.rc1 released

2015-03-30 Thread Jeroen Demeyer
On 2015-03-30 10:28, Simon King wrote: But how did they come there? I thought that meanwhile there is a separate folder for compiling Sage code. Those files still date from the time when there wasn't a separate folder. You can safely delete them. -- You received this message because you are su

[sage-release] Re: Sage 6.6.rc1 released

2015-03-30 Thread Volker Braun
On Monday, March 30, 2015 at 10:29:14 AM UTC+2, Simon King wrote: > > On 2015-03-30, Volker Braun > wrote: > > You can delete the extraneous files. > OK. But how did they come there? I thought that meanwhile there is a > separate folder for compiling Sage code. > They were in the .gitignore be

[sage-release] Re: Sage 6.6.rc1 released

2015-03-30 Thread Simon King
Hi Volker, On 2015-03-30, Volker Braun wrote: > You can delete the extraneous files. OK. But how did they come there? I thought that meanwhile there is a separate folder for compiling Sage code. > It seems you have the git rerere extension enabled Indeed I have. So, you can see that I am follo

[sage-release] Re: Sage 6.6.rc1 released

2015-03-30 Thread Volker Braun
You can delete the extraneous files. It seems you have the git rerere extension enabled which leads to a slightly different git output. You could add an appropriate ellipsis to the doctests... On Monday, March 30, 2015 at 10:17:04 AM UTC+2, Simon King wrote: > > Hi! > > "git status" gives me

[sage-release] Re: Sage 6.6.rc1 released

2015-03-30 Thread Simon King
Hi! "git status" gives me many "unbeobachtete Dateien": src/sage/categories/category.c src/sage/categories/category_with_axiom.c src/sage/misc/inputhook.c src/sage/misc/readline_extra_commands.c src/sage/rings/padics/padic_base_coercion.c src/sage/ri

[sage-release] Re: Sage 6.6.rc1 released

2015-03-27 Thread Emmanuel Charpentier
On a somewhat larger machine (Corei7, 16 Gb RAM, Debian testing), buids without a hitch (with preventive "make doc clean") and passes all tests. HTH, -- Emmanuel Charpentier Le vendredi 27 mars 2015 14:18:44 UTC+1, Emmanuel Charpentier a écrit : > > > > Le vendredi 27 mars 2015 01:52:57 UTC+1,

[sage-release] Re: Sage 6.6.rc1 released

2015-03-27 Thread Emmanuel Charpentier
This output is indeed incorrect in command line (same defect). A quick review of trac tickets show #10215 (most likely candidate), possibly #14428 ; #12279 or analogous might

[sage-release] Re: Sage 6.6.rc1 released

2015-03-27 Thread Eric Gourgoulhon
Le vendredi 27 mars 2015 18:16:18 UTC+1, Volker Braun a écrit : > > The tachyon output is the same as with (p1+p2).show(viewer='tachyon') on > the commandline. Thats just how Sage uses tachyon. > > Yes, the same (bad) tachyon output is obtained with versions of Sage much older than 6.6.rc1, e.

[sage-release] Re: Sage 6.6.rc1 released

2015-03-27 Thread Volker Braun
The tachyon output is the same as with (p1+p2).show(viewer='tachyon') on the commandline. Thats just how Sage uses tachyon. On Friday, March 27, 2015 at 3:04:23 PM UTC+1, Emmanuel Charpentier wrote: > > > > Le vendredi 27 mars 2015 14:30:56 UTC+1, Volker Braun a écrit : >> >> On Friday, March 27

[sage-release] Re: Sage 6.6.rc1 released

2015-03-27 Thread Volker Braun
On Friday, March 27, 2015 at 2:18:44 PM UTC+1, Emmanuel Charpentier wrote: > 3) 3D rendering in IPython notebook seems broken (curious results). > Please define. You mean tachyon (raytracing) output? I don't think the JSmol situation can be improved. -- You received this message because you a

[sage-release] Re: Sage 6.6.rc1 released

2015-03-27 Thread Emmanuel Charpentier
Le vendredi 27 mars 2015 01:52:57 UTC+1, Volker Braun a écrit : > > As usual, get the "develop" branch or the source tarball from > http://www.sagemath.org/download-latest.html > > 4087964 Updated Sage version to 6.6.rc1 > 713a8fe Trac #18048: Bug in GAP conversion of finite field elements > 2a0