[sage-devel] Windows release

[Erik Bray]

Earlier this week I finally had an opportunity to build a Windows
release for Sage 8.0 (which would have preferably been done before the
release announcement of 8.0 but things didn't work out
timing/communication-wise).

I uploaded the release binary to GitHub at:
https://github.com/sagemath/sage-windows/releases

Now the question is, how would I go about getting all the information
on sagemath.org updated, and ensuring that Windows builds are included
as part of the standard release process?  It would be nice to promote
this as the preferred way to run Sage on Windows, since for an average
user it should be the least hassle by far.  More advanced users might
still prefer other methods, which is fine too.

Thanks,
rik

-- 
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: Windows release

[Dima Pasechnik]

On Friday, August 11, 2017 at 9:28:59 AM UTC+1, Erik Bray wrote:
>
> Earlier this week I finally had an opportunity to build a Windows 
> release for Sage 8.0 (which would have preferably been done before the 
> release announcement of 8.0 but things didn't work out 
> timing/communication-wise). 
>
> I uploaded the release binary to GitHub at: 
> https://github.com/sagemath/sage-windows/releases 
>
> Now the question is, how would I go about getting all the information 
> on sagemath.org updated, 


Website updates are handled via https://github.com/sagemath/website
 

> and ensuring that Windows builds are included 
> as part of the standard release process?  It would be nice to promote 
> this as the preferred way to run Sage on Windows, since for an average 
> user it should be the least hassle by far.  More advanced users might 
> still prefer other methods, which is fine too. 
>
> Thanks, 
> rik 
>

-- 
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] Re: SIGSEGV in Maxima

[Eric Gourgoulhon]

Hi,

Le vendredi 11 août 2017 08:12:42 UTC+2, David Roe a écrit :
>
> Note that this is changed in https://trac.sagemath.org/ticket/23592
>

This is not the same part of manifolds code: #23592 
 deals with comparison of points 
(sage.manifolds.point.ManifoldPoint.__eq__), while the issue discussed here 
is related to assignment of tensor components 
(sage.tensor.modules.comp.CompWithSym.__setitem__). Since only nonzero 
components are stored, the test  
elif value == 0:
is performed in line 3263 of  src/sage/tensor/modules/comp.py
Now, as pointed by Ralf and similarly to what has been done in #23592, one 
could weaken this test to 
elif value.is_trivial_zero():
In this way, Maxima will not be called and, in addition to fixing the above 
bug, one could expect a significant speed-up.
I am going to open a ticket on this.

Eric.

-- 
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: Windows release

[aishen]

Thanks you very much for this release I was waiting for it to see how sage 
8 behaves on windows and linux
Best
Henri

Le vendredi 11 août 2017 10:28:59 UTC+2, Erik Bray a écrit :
>
> Earlier this week I finally had an opportunity to build a Windows 
> release for Sage 8.0 (which would have preferably been done before the 
> release announcement of 8.0 but things didn't work out 
> timing/communication-wise). 
>
> I uploaded the release binary to GitHub at: 
> https://github.com/sagemath/sage-windows/releases 
>
> Now the question is, how would I go about getting all the information 
> on sagemath.org updated, and ensuring that Windows builds are included 
> as part of the standard release process?  It would be nice to promote 
> this as the preferred way to run Sage on Windows, since for an average 
> user it should be the least hassle by far.  More advanced users might 
> still prefer other methods, which is fine too. 
>
> Thanks, 
> rik 
>

-- 
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] Re: SIGSEGV in Maxima

[Richard_L]

Eric, 
I will be happy to test as soon as source code is modified. Just let me 
know. 
 - Richard

On Friday, August 11, 2017 at 2:22:24 AM UTC-7, Eric Gourgoulhon wrote:
>
> Hi,
>
> Le vendredi 11 août 2017 08:12:42 UTC+2, David Roe a écrit :
>>
>> Note that this is changed in https://trac.sagemath.org/ticket/23592
>>
>
> This is not the same part of manifolds code: #23592 
>  deals with comparison of points 
> (sage.manifolds.point.ManifoldPoint.__eq__), while the issue discussed here 
> is related to assignment of tensor components 
> (sage.tensor.modules.comp.CompWithSym.__setitem__). Since only nonzero 
> components are stored, the test  
> elif value == 0:
> is performed in line 3263 of  src/sage/tensor/modules/comp.py
> Now, as pointed by Ralf and similarly to what has been done in #23592, one 
> could weaken this test to 
> elif value.is_trivial_zero():
> In this way, Maxima will not be called and, in addition to fixing the 
> above bug, one could expect a significant speed-up.
> I am going to open a ticket on this.
>
> Eric.
>
>

-- 
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: SIGSEGV in Maxima

[Richard_L]

That's a bit puzzling. In the Sage code, line 36 defines the manifold over 
the real field. That is supposed to be inherited by the chart in line 39:

M = Manifold(1*3,'R^3',field='real',start_index=1)
U = M.open_subset('U')

Rho. = U.chart("r12:(0,+oo) r13:(0,+oo) r23:(0,+oo)")

One therefore expects r12, etc. to be real.
 - Richard

On Thursday, August 10, 2017 at 10:34:40 PM UTC-7, Robert Dodier wrote:
>
> On 2017-08-10, Richard_L > wrote: 
>
> > The following string sent to maxima causes a seg-fault and core dump: 
>
> > '#$is 
> > 
> (equal(-(_SAGE_VAR_r13^2*_SAGE_VAR_r23-_SAGE_VAR_r23^3)/((-_SAGE_VAR_r23^4)+2*_SAGE_VAR_r13^2*_SAGE_VAR_r23^2-_SAGE_VAR_r13^4+_SAGE_VAR_r12^4),0))$'
>  
>
>
> Looks like domain:complex and assume are both needed to trigger this 
> error. declare(..., real) isn't needed to trigger it. 
>
>  ... 
>
> A workaround might be to set domain:real instead of domain:complex. 
>
> If someone can make a bug report and include these notes, that would be 
> great. I didn't try to find a simpler example but maybe one exists. 
>
> best, 
>
> Robert Dodier 
>
>

-- 
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] Patchbot raises error but status is still shown as pending.

[Maarten Derickx]

Hi,

At https://patchbot.sagemath.org/ticket/23610/ you can see that the 
patchbot status of two different patchbots is mentioned as pending in all 
the tests listed on that page. However if you look at one of the logs 

 you 
will see that an "SkipTicket("unsafe")" error is raised in both cases. So I 
have two questions:

1) Is this wanted behaviour of the patchbot?
2) Why is the ticket considered unsafe? Is it because the ticket modifies 
the doctesting framework? A more detailed error message would be useful.

-- 
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: SIGSEGV in Maxima

[Eric Gourgoulhon]

Le vendredi 11 août 2017 16:21:45 UTC+2, Richard_L a écrit :
>
> That's a bit puzzling. In the Sage code, line 36 defines the manifold over 
> the real field. That is supposed to be inherited by the chart in line 39:
>
> M = Manifold(1*3,'R^3',field='real',start_index=1)
> U = M.open_subset('U')
>
> Rho. = U.chart("r12:(0,+oo) r13:(0,+oo) r23:(0,+oo)")
>
> One therefore expects r12, etc. to be real.
>
>  
Indeed, for a real manifold, U.chart("r12:(0,+oo) ...") does the following:

r12 = SR.var("r12", domain='real')
assume(r12, 'real')
assume(r12 > 0)

Eric.

-- 
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] Re: SIGSEGV in Maxima

[Eric Gourgoulhon]

Le vendredi 11 août 2017 15:30:08 UTC+2, Richard_L a écrit :
>
> Eric, 
> I will be happy to test as soon as source code is modified. Just let me 
> know. 
>

For sure I will. Thanks.

Eric. 

-- 
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] polytopes_db not on the mirrors?

[Vincent Delecroix]

Got the following

[Errno 404] Not Found: 
'//sagepad.org/spkg/upstream/polytopes_db/polytopes_db-20170220.tar.bz2'


Vincent

--
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] failure installing giac (version 1.2.3.47.p0)

[Vincent Delecroix]

see attached log

Vincent

--
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.
Found local metadata for giac-1.2.3.47.p0
Using cached file /home/vdelecro/sage_patchbot/upstream/giac-1.2.3.47.tar.bz2
giac-1.2.3.47.p0

Setting up build directory for giac-1.2.3.47.p0
Finished extraction
Applying patches from ../patches...
Applying ../patches/cSolveorder-check.patch
patching file check/TP16-sol.cas.out1
Applying ../patches/libpng16.patch
patching file configure.in
patching file configure
Applying ../patches/macos-ifactor.patch
patching file src/ifactor.cc
Applying ../patches/nofltk-check.patch
patching file check/testgeo
patching file check/TP00-sol.cas
patching file check/TP00-sol.cas.out1
patching file check/TP02-sol.cas
patching file check/TP09-sol.cas
patching file check/TP19-sol.cas

Host system:
Linux quasar 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:38:41 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

C compiler: gcc
C compiler version:
Using built-in specs.
COLLECT_GCC=/usr/bin/gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/5/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 5.4.0-6ubuntu1~16.04.4' --with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-5 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-5-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) 

Configuring giac...
configure: WARNING: you should use --build, --host, --target
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking whether ln -s works... yes
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... ld
checking if the linker (ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for ld option to reload object files... -r
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking how to run the C preprocessor... gcc -E
checking for ANSI C header fil

Re: [sage-devel] failure installing giac (version 1.2.3.47.p0)

[François Bissey]

Hum, it wants to re-run parts of autoconf to regenerate configure.
There may be a time stamp issue.

François

> On 12/08/2017, at 09:01, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
> 
> see attached log
> 
> Vincent
> 
> -- 
> 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.

[sage-devel] Re: polytopes_db not on the mirrors?

[Volker Braun]

Maybe review https://trac.sagemath.org/ticket/22400 first? ;P

On Friday, August 11, 2017 at 10:58:57 PM UTC+2, vdelecroix wrote:
>
> Got the following 
>
> [Errno 404] Not Found: 
> '//sagepad.org/spkg/upstream/polytopes_db/polytopes_db-20170220.tar.bz2' 
>
> Vincent 
>

-- 
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: SIGSEGV in Maxima

[Richard_L]

Clearly Robert has found a bug in maxima. Here's a little test further to 
my earlier "puzzle":
If I write in sage as follows:
#$is 
(equal(-(_SAGE_VAR_r13^2*_SAGE_VAR_r23-_SAGE_VAR_r23^3)/((-_SAGE_VAR_r23^4)+2*_SAGE_VAR_r13^2*_SAGE_VAR_r23^2-_SAGE_VAR_r13^4+_SAGE_VAR_r12^4),0))$

var('r12 r13 r23',domain='complex')
assume(r12>0, r13>0, r23>0)

#trace( "bool(-(r13^2*r23-r23^3)/((-r23^4)+2*r13^2*r23^2-r13^4+r12^4) == 
0)" )
bool(-(r13^2*r23-r23^3)/((-r23^4)+2*r13^2*r23^2-r13^4+r12^4) == 0)

then sage finishes without error! Instead, it returns "False".
Dropping into pydb, I recover the identical *statement* being shipped off 
to Maxima!
> 
/home/rllozes/sage-8.0/local/lib/python2.7/site-packages/sage/interfaces/maxima_lib.py(452)_eval_line()
450 line = line[ind_semi+1:]
451 if statement:
5-> 452 result = ((result + '\n') if result else '') + 
max_to_string(maxima_eval("#$%s$"%statement))
453 else:
454 statement = line[:ind_dollar]

ipdb> p statement
'is 
(equal(-(_SAGE_VAR_r13^2*_SAGE_VAR_r23-_SAGE_VAR_r23^3)/((-_SAGE_VAR_r23^4)+2*_SAGE_VAR_r13^2*_SAGE_VAR_r23^2-_SAGE_VAR_r13^4+_SAGE_VAR_r12^4),0))'

This behavior is independent of whether the variables are declared 'real' 
or 'complex'. 
Conclusion: something else is going on in manifolds and/or in maxima. 

Robert, what version of maxima did you test?
 - Richard

-- 
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.