[sage-devel] Error with Parallelism, case of nproc>1

2019-03-14 Thread Richard_L
Continuing with the example first discussed on ask.sagemath.org and graciously corrected/answered by Eric G, I now find that setting *nproc* to anything but *1* in the following will cause the last line to give incorrect results. I am running sagemath version 8.5. According to trac, this

Re: [sage-devel] Re: internet tests failing

2019-03-14 Thread Dima Pasechnik
On Thu, Mar 14, 2019 at 7:51 PM John H Palmieri wrote: > > I'm seeing the same failure on a Mac running the most recent OS X. I have > openssl 1.1.1a installed on this machine, and I see the error in Sage. Then I > did './sage -i openssl' and './sage -f python2', and I still see the error. >

[sage-devel] Re: pretty print latex doctest error

2019-03-14 Thread John H Palmieri
On Thursday, March 14, 2019 at 1:46:38 PM UTC-7, kcrisman wrote: > > I just ran the following command, and amazingly got only one timeout and > one error. The rest is fine. > > ./sage -tp 3 -T 600 --optional=sage,python2,latex src/sage > >

[sage-devel] pretty print latex doctest error

2019-03-14 Thread kcrisman
I just ran the following command, and amazingly got only one timeout and one error. The rest is fine. ./sage -tp 3 -T 600 --optional=sage,python2,latex src/sage ** File "src/sage/repl/rich_output/pretty_print.py", line 217,

Re: [sage-devel] Re: internet tests failing

2019-03-14 Thread kcrisman
Perhaps it's some sort of certificate issue. > If an up to date openssl has its certs improperly set up, it won't work, > IMHO. > >> >> Give the error message, this seems plausible. Any ideas on where to go from here? Is it user error for me to try to use the OEIS through Sage? Volker is

Re: [sage-devel] Re: internet tests failing

2019-03-14 Thread Dima Pasechnik
Perhaps it's some sort of certificate issue. If an up to date openssl has its certs improperly set up, it won't work, IMHO. On Thu, 14 Mar 2019 19:51 John H Palmieri, wrote: > I'm seeing the same failure on a Mac running the most recent OS X. I have > openssl 1.1.1a installed on this machine,

[sage-devel] Re: internet tests failing

2019-03-14 Thread John H Palmieri
I'm seeing the same failure on a Mac running the most recent OS X. I have openssl 1.1.1a installed on this machine, and I see the error in Sage. Then I did './sage -i openssl' and './sage -f python2', and I still see the error. The Python 2 log file does not list ssl among the modules which

Re: [sage-devel] Something is wrong with my installed sage

2019-03-14 Thread Dima Pasechnik
On Thu, Mar 14, 2019 at 5:44 PM Ai Bo wrote: > > I see. Thank you. > As I don't know how and when the files will be cleaned on the local disk and > I don't know when my program, if launched at local disk, will be killed. A typical HPC center policy with scratch disks is that files live a

[sage-devel] Re: internet tests failing

2019-03-14 Thread Volker Braun
I'm guessing you run this on an oldish mac, those have an outdated openssl that doesn't support TLS12. More and more sites are switching that on. Building Sage's openssl should fix that. On Thursday, March 14, 2019 at 7:09:50 PM UTC+1, kcrisman wrote: > > This could be just me. But I am

[sage-devel] internet tests failing

2019-03-14 Thread kcrisman
This could be just me. But I am getting a lot of this when I try running optional internet tests for e.g. src/sage/databases/oeis.py or src/sage/symbolic/integration/external.py Internet clearly works if you can read this message, but apparently it doesn't work from within Sage, because I

Re: [sage-devel] Something is wrong with my installed sage

2019-03-14 Thread Ai Bo
I see. Thank you. As I don't know how and when the files will be cleaned on the local disk and I don't know when my program, if launched at local disk, will be killed. I downloaded the binary package. I am a little bit confused. Does the binary package know where I already build ./sage? On Thu,

Re: [sage-devel] Re: schedule for 8.7 rc and final release

2019-03-14 Thread Volker Braun
Feel free to fix the Cygwin-related bugs, but some of these are longstanding issues that should be discussed with upstream first; Realistically thats not going to make it to the next Sage version. On Thursday, March 14, 2019 at 2:36:29 PM UTC+1, E. Madison Bray wrote: > > Hi Volker, > > I

[sage-devel] Re: Sage 8.4 has broken Hilbert polynomials

2019-03-14 Thread Simon King
Hi John, sorry, somehow I missed your posting. Le lundi 5 novembre 2018 18:55:25 UTC+1, john_perry_usm a écrit : > > This code works in Sage 8.3, but not in Sage 8.4. > > P. = PolynomialRing(QQ) > I = Ideal([x^3, x*y^2, y^4, x^2*y*z, y^3*z, x^2*z^2, x*y*z^2, x*z^3]) >

Re: [sage-devel] Re: Incorrect double integral result

2019-03-14 Thread Christopher Subich
On 3/14/19 8:54 AM, kcrisman wrote: Following up, does this computation make any sense?  Presumably this is the core issue. That computation makes sense, it's the second integration that breaks: (x,y) = var('x y') z = sqrt(1-x^2-y^2) print(z) assume(abs(x)<1) assume(abs(y)<1) zint_y =

Re: [sage-devel] another "cp: cannot overwrite non-directory '[..]./lib64' with directory"

2019-03-14 Thread E. Madison Bray
On Thu, Mar 14, 2019 at 4:50 PM E. Madison Bray wrote: > > On Thu, Mar 14, 2019 at 4:37 PM E. Madison Bray wrote: > > > > On Thu, Mar 14, 2019 at 4:23 PM Dima Pasechnik wrote: > > > > > > > > > > > > On Thu, 14 Mar 2019 15:17 E. Madison Bray, wrote: > > >> > > >> On Thu, Mar 14, 2019 at 12:06

Re: [sage-devel] another "cp: cannot overwrite non-directory '[..]./lib64' with directory"

2019-03-14 Thread E. Madison Bray
On Thu, Mar 14, 2019 at 4:37 PM E. Madison Bray wrote: > > On Thu, Mar 14, 2019 at 4:23 PM Dima Pasechnik wrote: > > > > > > > > On Thu, 14 Mar 2019 15:17 E. Madison Bray, wrote: > >> > >> On Thu, Mar 14, 2019 at 12:06 AM Dima Pasechnik wrote: > >> > > >> > It's reproducible on my Linux

Re: [sage-devel] another "cp: cannot overwrite non-directory '[..]./lib64' with directory"

2019-03-14 Thread Dima Pasechnik
I just added cmake to our "spkg-configure-wanted" list On Thu, 14 Mar 2019 15:37 E. Madison Bray, wrote: > On Thu, Mar 14, 2019 at 4:23 PM Dima Pasechnik wrote: > > > > > > > > On Thu, 14 Mar 2019 15:17 E. Madison Bray, > wrote: > >> > >> On Thu, Mar 14, 2019 at 12:06 AM Dima Pasechnik >

Re: [sage-devel] another "cp: cannot overwrite non-directory '[..]./lib64' with directory"

2019-03-14 Thread E. Madison Bray
On Thu, Mar 14, 2019 at 4:23 PM Dima Pasechnik wrote: > > > > On Thu, 14 Mar 2019 15:17 E. Madison Bray, wrote: >> >> On Thu, Mar 14, 2019 at 12:06 AM Dima Pasechnik wrote: >> > >> > It's reproducible on my Linux machine, and I see that >> > "non-directory '/opt/sage/local/./lib64'" is a

Re: [sage-devel] another "cp: cannot overwrite non-directory '[..]./lib64' with directory"

2019-03-14 Thread Dima Pasechnik
On Thu, 14 Mar 2019 15:17 E. Madison Bray, wrote: > On Thu, Mar 14, 2019 at 12:06 AM Dima Pasechnik wrote: > > > > It's reproducible on my Linux machine, and I see that > > "non-directory '/opt/sage/local/./lib64'" is a symbolic link. > > > > removing it manually allows the install to complete.

Re: [sage-devel] another "cp: cannot overwrite non-directory '[..]./lib64' with directory"

2019-03-14 Thread E. Madison Bray
On Thu, Mar 14, 2019 at 12:06 AM Dima Pasechnik wrote: > > It's reproducible on my Linux machine, and I see that > "non-directory '/opt/sage/local/./lib64'" is a symbolic link. > > removing it manually allows the install to complete. > (whether it breaks anything I don't know, but should not be

Re: [sage-devel] another "cp: cannot overwrite non-directory '[..]./lib64' with directory"

2019-03-14 Thread E. Madison Bray
On Thu, Mar 14, 2019 at 12:06 AM Dima Pasechnik wrote: > > It's reproducible on my Linux machine, and I see that > "non-directory '/opt/sage/local/./lib64'" is a symbolic link. > > removing it manually allows the install to complete. > (whether it breaks anything I don't know, but should not be

[sage-devel] Re: Sage python3 doctests

2019-03-14 Thread kcrisman
> I wanted to run some doctests with my Python 3 Sage installation. > However, running "sage -t" results in > > Using --optional=dochtml,memlimit,mpir,python2,sage > > ie, python2 is in the list. Is that expected? How should I > run the tests? > On a related note, I was attempting to

[sage-devel] Re: Sage 8.4 has broken Hilbert polynomials

2019-03-14 Thread jplab
This still does not work in Sage version 8.7.beta7. I have created a ticket located at https://trac.sagemath.org/ticket/27483 Best regards, Le lundi 5 novembre 2018 18:55:25 UTC+1, john_perry_usm a écrit : > > This code works in Sage 8.3, but not in Sage 8.4. > > P. = PolynomialRing(QQ) >

Re: [sage-devel] Re: schedule for 8.7 rc and final release

2019-03-14 Thread E. Madison Bray
Hi Volker, I don't think there should be a release candidate at least until most of the blocker issues [1] are resolved; in particular the four that are already either positively reviewed or are in-progress. Thanks [1]

[sage-devel] Re: schedule for 8.7 rc and final release

2019-03-14 Thread Volker Braun
Next develop release will be rc0 IMHO changes to gmpy2 should wait until the next version to give it some time to test out. -- 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

[sage-devel] schedule for 8.7 rc and final release

2019-03-14 Thread Vincent Delecroix
Dear Volker, Do you have a rough schedule for the next Sage release? I am interested because Vincent K is putting a lot of effort towards having a new release of gmpy2 [1] that would be great to have in 8.7. [1] https://github.com/aleaxit/gmpy/issues/199 Cheers Vincent -- You received this

[sage-devel] Re: Incorrect double integral result

2019-03-14 Thread kcrisman
On Wednesday, March 13, 2019 at 7:11:02 PM UTC-4, Emmanuel Charpentier wrote: > > This integral turns out to be anything but trivial. > > Neither Sympy, Giac nor Fricas can solve it, in its original form nor in > polar coordinates. BTW, neither Mathematica nor Rubi running on Mathematica >

[sage-devel] Re: polymake-3.1 build fails with std::__::numeric_limits<...>

2019-03-14 Thread jplab
Dear Harly Hallikas, This error seems to be in polymake source code. You could report this compilation error to the polymake development team here: https://forum.polymake.org/ to see if this fixed in the current version. The current version is 3.3 available here:

[sage-devel] Failing doctest in src/sage/rings/integer.pyx

2019-03-14 Thread jonathan.kliem via sage-devel
I'm getting the same error as in #26002 in src/sage/rings/integer.pyx In my patchbot run https://patchbot.sagemath.org/log/0/debian/9.8/x86_64/4.9.0-8-amd64/cofio/2019-03-13%2016:31:01 this just appeared as slow, but I don't see that this test should

Re: [sage-devel] Something is wrong with my installed sage

2019-03-14 Thread Dima Pasechnik
On Thu, Mar 14, 2019 at 7:24 AM Dima Pasechnik wrote: > > On Thu, Mar 14, 2019 at 7:09 AM Dima Pasechnik wrote: > > > > On Thu, Mar 14, 2019 at 3:39 AM Ai Bo wrote: > > > > > > Sorry, it doesn't work if I build on local disk and then copy to /nfs. > > > I got error: > > > bash-4.3$ ./sage > >

Re: [sage-devel] Something is wrong with my installed sage

2019-03-14 Thread Dima Pasechnik
On Thu, Mar 14, 2019 at 7:09 AM Dima Pasechnik wrote: > > On Thu, Mar 14, 2019 at 3:39 AM Ai Bo wrote: > > > > Sorry, it doesn't work if I build on local disk and then copy to /nfs. > > I got error: > > bash-4.3$ ./sage But did you try moving it back to the local disk, before starting it?

Re: [sage-devel] Something is wrong with my installed sage

2019-03-14 Thread Dima Pasechnik
On Thu, Mar 14, 2019 at 3:39 AM Ai Bo wrote: > > Sorry, it doesn't work if I build on local disk and then copy to /nfs. > I got error: > bash-4.3$ ./sage > > ERROR: The Sage installation tree has moved > > from /tmp/.../sage-8.6 > to /nfs/.../Sage/sage-8.6 > > This is not supported, and Sage