Re: [sage-devel] R 3.3.1 depends on a SSL/TLS implementation

A couple of quick notes ; consistent answer to follow (not soon, alas...) : Le mardi 1 novembre 2016 03:23:41 UTC+1, William a écrit : > > On Mon, Oct 31, 2016 at 6:58 PM, kcrisman > > wrote: > > All I know is this: > > > > 1) We have "sold" a lot of Sage by saying it's all in there, and at >

Re: [sage-devel] R 3.3.1 depends on a SSL/TLS implementation

On Mon, Oct 31, 2016 at 6:58 PM, kcrisman wrote: > All I know is this: > > 1) We have "sold" a lot of Sage by saying it's all in there, and at least > some people have used Sage+R effectively. Estimates of how many vary > wildly. But non-zero. Nobody is suggesting deprecating the potential to u

Re: [sage-devel] Re: jsmol.js

On Mon, Oct 31, 2016 at 7:11 PM, kcrisman wrote: > > >>https://github.com/jupyterhub/jupyterhub/issues/401 >> >> which blocks 3d graphics in jupyter/sage working at all for sage and >> jupyter hub: >> >>https://github.com/sagemathinc/smc/issues/159 >> >> It seems like according to >> https

[sage-devel] Re: Bug: Sage says Maxima was unable to solve this BVP but it's not true!

I opened https://trac.sagemath.org/ticket/21789 for this. -- 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

[sage-devel] Re: jsmol.js

https://github.com/jupyterhub/jupyterhub/issues/401 > > which blocks 3d graphics in jupyter/sage working at all for sage and > jupyter hub: > >https://github.com/sagemathinc/smc/issues/159 > > It seems like according to > https://github.com/jupyterhub/jupyterhub/issues/401 >

Re: [sage-devel] R 3.3.1 depends on a SSL/TLS implementation

All I know is this: 1) We have "sold" a lot of Sage by saying it's all in there, and at least some people have used Sage+R effectively. Estimates of how many vary wildly. But non-zero. 2) rpy2 might be there, but as far as I can tell most people who've used Sage+R use it via the "dumb pexpect

[sage-devel] Re: vote on behaviour of is_similar for matrices

I expect that (1) If M is not square, then there is no ".is_similar" method attached to M. (2) If M is square and N has different size, then raise an error. If False is returned in the case (2), then the user needs to make additional efforts to find the cause (either N has the same size but is

Re: [sage-devel] sage 7.4 does not build on Ubuntu 16.10

There is currently an issue with brial and gcc 6.2.0 that remains to be fixed. I don’t remember if someone blacklisted that gcc as a consequence. I should do something about that, even if it is a bit radical. François > On 1/11/2016, at 09:55, William Stein wrote: > > On Mon, Oct 31, 2016 at 1

Re: [sage-devel] sage 7.4 does not build on Ubuntu 16.10

On Mon, Oct 31, 2016 at 1:16 PM, François Bissey wrote: > Yes, building gcc 4.9.3 with gcc 6.2.0 is not exactly supported. I set nothing and just went with Sage defaults. What a mess... > > > On 01/11/16 09:09, William Stein wrote: >> >> I tried to install sage-7.4 on a clean new Ubuntu:16.10 d

Re: [sage-devel] sage 7.4 does not build on Ubuntu 16.10

Yes, building gcc 4.9.3 with gcc 6.2.0 is not exactly supported. On 01/11/16 09:09, William Stein wrote: I tried to install sage-7.4 on a clean new Ubuntu:16.10 docker container (on 64-bit x68 intel). It fails trying to building GCC with ... gcc-4.9.3.p1] (cd '/home/w/sage-7.4/local/var/tmp/

Re: [sage-devel] Trac error on push

On 01/11/16 07:31, jhonrubia6 wrote: Thank you. Is there any place where is documented how to get the new ssh key for the host whenever this happens again? I don't know that's published anywhere at the present time. Anyone? Francois -- You received this message because you are subscribed to t

Re: [sage-devel] sage 7.4 does not build on Ubuntu 16.10

(I'm new to posting in these groups so I apologize in advance if I am misplacing my query.) I'd also love to know how to work around this. If the thread moved elsewhere, please post a pointer here. Many thanks, Thomas On Thursday, October 20, 2016 at 11:21:52 AM UTC-4, Herbert Eisenbeis wrote

Re: [sage-devel] Trac error on push

Thank you. Is there any place where is documented how to get the new ssh key for the host whenever this happens again? El lunes, 31 de octubre de 2016, 8:54:29 (UTC+1), François escribió: > > Add > trac.sagemath.org,104.197.143.230 ecdsa-sha2-nistp256 > E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzd

Re: [sage-devel] plot3d Assertion Error in Jupyter Notebook

For what it's worth, you could use SageMathCloud https://cloud.sagemath.com/projects/4a5f0542-5873-4eed-a85c-a18c706e8bcd/files/support/2016-10-31-083104%20%20plot3d%20Assertion%20Error.sagews Which you can install locally via docker: https://github.com/sagemathinc/smc/blob/master/src/dev/do

[sage-devel] plot3d Assertion Error in Jupyter Notebook

Evaluating the command below in Jupyter Notebook throws an Assertion Error but evaluating it the Sage Notebook executes without any error. Specifically, it is caused by setting the mesh argument to True. it plots without any error without the mesh argument. How do I fix it? var('y') plot3d(sin

Re: [sage-devel] Re: (1/(1006987929*pi - 3163545880)).n() raises division by zero error

A possible way out sage: a = 1 / (1006987929*pi - 3163545880) sage: continued_fraction(a).n() 3.23899542780221e6 And the estimation above is accurate (contrarily to what is being done in the symbolic ring). On 31 October 2016 at 13:53, Sébastien Labbé wrote: > I just created https://trac.sagem

[sage-devel] Re: (1/(1006987929*pi - 3163545880)).n() raises division by zero error

I just created https://trac.sagemath.org/ticket/21788 -- 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 grou

[sage-devel] (1/(1006987929*pi - 3163545880)).n() raises division by zero error

Using 7.4.beta6, I get sage: (1/(1006987929*pi - 3163545880)).n() Traceback (most recent call last) in () > 1 a.n() src/sage/structure/element.pyx in sage.structure.element.Element.n (build/cythonized/sage/structure/element.c:6862)() 642 0.667 643 ""

[sage-devel] Re: JModelica.org in Sage

Hello Johan, I was wondering if this happened and I can use JModelica on Sage. I have created a Docker container for JModelica. It simply means that you can instantly have a computer with JModelica installed. You can run the container with this command: docker run -p : mechatronics3d/

Re: [sage-devel] Re: Testing corner cases

On Mon, 31 Oct 2016, Jakob Kroeker wrote: So you have a mind of a tester? That's good to  know.  Well, my "trivialcase-tester" is just those few lines of code. But as you can see from https://trac.sagemath.org/ticket/21741 , it found quite many error from graphs. In matrices I did not found

[sage-devel] Re: Testing corner cases

@Jori Mäntysalo So you have a mind of a tester? That's good to know. In general I think it would be good to have a random testing framework together with a testbot in sage. I'm working on that in Singular and Macaulay2 and already catche

Re: [sage-devel] Trac error on push

That worked. Thanks again. On Monday, October 31, 2016 at 4:54:29 PM UTC+9, François wrote: > > Add > trac.sagemath.org,104.197.143.230 ecdsa-sha2-nistp256 > E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBG+/AO490umZWuczUgClP4BgFm5XR9I43z4kf9f+pu8Uj6UvH/7Pz1oBkJ71xET+xTmecBHB2c9OwlgPjB70AB

Re: [sage-devel] Trac error on push

Add trac.sagemath.org,104.197.143.230 ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBG+/AO490umZWuczUgClP4BgFm5XR9I43z4kf9f+pu8Uj6UvH/7Pz1oBkJ71xET+xTmecBHB2c9OwlgPjB70AB8= as a single line at the end of .ssh/know_hosts François > On 31/10/2016, at 20:52, Marco Cognetta

Re: [sage-devel] Trac error on push

There is no longer a line with trac.sagemath.org but when I try to connect I do not get the option of adding it to the list of known_hosts. I had this problem a few weeks ago and was able to fix it but I have forgotten how... Thanks for your help thus far! On Monday, October 31, 2016 at 4:36:35

Re: [sage-devel] Trac error on push

Then, it may have been the wrong host. You should remove the line starting with trac.sagemath.org Once removed, the next time you connect to the trac server, you will be asked about adding it to the list of know_hosts. François > On 31/10/2016, at 20:27, Marco Cognetta wrote: > > I have done t

Re: [sage-devel] Re: Multivariate polynomial factoring and bug(?)

On Sun, 30 Oct 2016, parisse wrote: I guess that the heuristics used by Singular for sparse multivariate factorization did not succeed for this polynomial (this pair is slightly more complicated than the previous pairs), and reverted to dense factorization (probably Hensel lift algorithm), whi

Re: [sage-devel] Trac error on push

I have done that but I still get the same error. How do I get the correct information to put in known_hosts? On Monday, October 31, 2016 at 4:14:23 PM UTC+9, François wrote: > > Removing the 4th line in your file > ~/.ssh/known_hosts > looks like it would do the trick. > I think it would be th

Re: [sage-devel] Trac error on push

Removing the 4th line in your file ~/.ssh/known_hosts looks like it would do the trick. I think it would be the 4th line but it could be another one. It will almost certainly be another one for other people. François > On 31/10/2016, at 20:10, Marco Cognetta wrote: > > What is the fix for this

Re: [sage-devel] Trac error on push

What is the fix for this? I have tried getting the updated trac and testing my rsa keys. On Saturday, October 29, 2016 at 2:33:05 AM UTC+9, Dima Pasechnik wrote: > > > > On Friday, October 28, 2016 at 5:01:54 PM UTC, jhonrubia6 wrote: >> >> Is not 104.197.143.230? >> >> >> OnoSendaiII:sage J_Honr