[sage-devel] Re: Caching considered controversial

2012-09-13 Thread Simon King
Hi Nils, On 2012-09-13, Nils Bruin wrote: > Identity-based caching as applied in the coercion framework is a > little easier to reason about (although, as we found, still quite > tricky to implement), but that's only meaningful in the presence of > guaranteed global uniqueness No, that's not tru

[sage-devel] Re: Caching considered controversial

2012-09-13 Thread Simon King
On 2012-09-14, Nils Bruin wrote: > On Sep 13, 4:48 pm, Volker Braun wrote: >> The UniqueRepresentation issue is slightly more tricky. If you follow the >> "no __hash__" route then you can't use them as arguments to objects with >> unique representation. +1, as I have already stated in my previou

[sage-devel] Re: CTRL-C crashes the notebook in 5.3

2012-09-13 Thread Keshav Kini
Daniel Smertnig writes: > AFAIK the only reason 5.3 shipped with pyOpenSSL 0.12 was that 0.13 > has problem with older OpenSSL versions (<0.9.8f or something). This > is not an issue on Ubuntu, so pyOpenSSL 0.13 should be safe to use. > Of course, if you don't upgrade, the SSL notebook will not wo

[sage-devel] Another /bin/bash error

2012-09-13 Thread Stephen Montgomery-Smith
While trying to compile sage-5.4beta1 on FreeBSD, it failed because of another place using "#!/bin/bash". As I understand it, it should be "#!/usr/bin/env bash". This time it is in fflas_ffpack-1.6.0//src/fflas-ffpack-config.in I'll file a ticket (except trac.sage isn't working for me right n

[sage-devel] Re: Caching considered controversial

2012-09-13 Thread Nils Bruin
On Sep 13, 4:48 pm, Volker Braun wrote: > The UniqueRepresentation issue is slightly more tricky. If you follow the > "no __hash__" route then you can't use them as arguments to objects with > unique representation. We either demand that == always means identical > (often not convenient at the com

[sage-devel] Re: Caching considered controversial

2012-09-13 Thread Volker Braun
On Thursday, September 13, 2012 11:06:50 PM UTC+1, Nils Bruin wrote: > > > Really, the issue is that the objects violate the contract on > > object.__hash__(): > Well, that is a problem, but not the main one I wanted to point out. > I claim that it is the only problem here. Really, objects that

[sage-devel] Re: Modular fibration animated with Sage

2012-09-13 Thread Jason Grout
On 9/13/12 5:06 PM, Jason Grout wrote: I think there is still a lot of room for speeding this up more, if someone wanted a fun project. And I got another factor of 2 by making the inner function a Cython "class" [1]: http://aleph.sagemath.org/?q=8b878cda-030d-4433-9d11-a10153d9d9a3 Okay, t

[sage-devel] Re: Modular fibration animated with Sage

2012-09-13 Thread Jason Grout
On 9/13/12 3:09 PM, Jason Grout wrote: On 9/13/12 2:45 PM, Niles Johnson wrote: Lastly, there's a heartwarming example of the benefits of open development here: I made all of the Sage code for my animation public, and I deliberately tried to use open-source software for the entire project so th

[sage-devel] Re: Caching considered controversial

2012-09-13 Thread Nils Bruin
On Sep 13, 9:51 am, Volker Braun wrote: > On Thursday, September 13, 2012 5:19:57 PM UTC+1, Nils Bruin wrote: > > sage: A==B > > True > > sage: hash(A) > > 0 > > sage: hash(B) > > 44546084519852655 > > Really, the issue is that the objects violate the contract on > object.__hash__(): Well, that i

[sage-devel] Re: Modular fibration animated with Sage

2012-09-13 Thread Jason Grout
On 9/13/12 2:45 PM, Niles Johnson wrote: Lastly, there's a heartwarming example of the benefits of open development here: I made all of the Sage code for my animation public, and I deliberately tried to use open-source software for the entire project so that someone else could easily use the cod

[sage-devel] Modular fibration animated with Sage

2012-09-13 Thread Niles Johnson
Hello Sage developers! Some time ago I made an animation of the Hopf fibration using Sage. Recently, a graduate of the African Institute for Mathematical Sciences has finished animating a different map from S^3 to S^2. Ihechukwu Chinyere worked with Bruce Bartlett there and made an animation

Re: [sage-devel] Re: CTRL-C crashes the notebook in 5.3

2012-09-13 Thread Daniel Smertnig
On Thursday, September 13, 2012 6:43:05 PM UTC+2, Jan Groenewald wrote: > > > Is it clear that the segfault is harmless to your sage session, > computations, and data? > Would it be a good idea to go ahead and update the PPA anyway? > AFAIK the only reason 5.3 shipped with pyOpenSSL 0.12 was that

[sage-devel] Re: Caching considered controversial

2012-09-13 Thread Volker Braun
On Thursday, September 13, 2012 5:19:57 PM UTC+1, Nils Bruin wrote: > sage: A==B > True > sage: hash(A) > 0 > sage: hash(B) > 44546084519852655 Really, the issue is that the objects violate the contract on object.__hash__(): "The only required property is that objects which compare equal

[sage-devel] Re: Caching considered controversial

2012-09-13 Thread Simon King
Hi Nils, On 2012-09-13, Nils Bruin wrote: > There seems to be a big push to use caching in a lot of places in > sage. There, a problem arises from the fact that sage's conventions > for equality tests are rather liberal. This of course isn't an argument against caching in general. Actually, from

Re: [sage-devel] Re: CTRL-C crashes the notebook in 5.3

2012-09-13 Thread Jan Groenewald
Hi On 13 September 2012 18:19, P Purkayastha wrote: > On 09/13/2012 09:29 PM, Jan Groenewald wrote: > >> Hi >> >> I get this problem with both source and binary. A previous thread about >> the same problem in 5.2 >> https://groups.google.com/**forum/?fromgroups#!topic/sage-** >> devel/CPgiZ2d7uM

[sage-devel] Re: CTRL-C crashes the notebook in 5.3

2012-09-13 Thread P Purkayastha
On 09/13/2012 09:29 PM, Jan Groenewald wrote: Hi I get this problem with both source and binary. A previous thread about the same problem in 5.2 https://groups.google.com/forum/?fromgroups#!topic/sage-devel/CPgiZ2d7uMQ said that a pyopenssl update fixes it. I never tried it, I just waited for th

[sage-devel] Caching considered controversial

2012-09-13 Thread Nils Bruin
There seems to be a big push to use caching in a lot of places in sage. There, a problem arises from the fact that sage's conventions for equality tests are rather liberal. Obviously, one should only cache functions that solely depend on the equality class of their argument. That's probably less o

[sage-devel] Re: pari_close causing segfault

2012-09-13 Thread Simon King
Hi Jason, On 2012-09-13, Jason Grout wrote: > I've rewritten the code for moving to the new IPython to make it more > flexible, and I'm running into a puzzling problem. When I call > quit_sage from an exit handler, for some reason the pari_close() call > happening inside the pari._unsafe_deal

[sage-devel] pari_close causing segfault

2012-09-13 Thread Jason Grout
I've rewritten the code for moving to the new IPython to make it more flexible, and I'm running into a puzzling problem. When I call quit_sage from an exit handler, for some reason the pari_close() call happening inside the pari._unsafe_deallocate_pari_stack function causes a segfault. This o

Re: [sage-devel] Re: CTRL-C crashes the notebook in 5.3

2012-09-13 Thread Jan Groenewald
Hi I get this problem with both source and binary. A previous thread about the same problem in 5.2 https://groups.google.com/forum/?fromgroups#!topic/sage-devel/CPgiZ2d7uMQ said that a pyopenssl update fixes it. I never tried it, I just waited for the next Sage version with an updated pyopenssl. I

Re: [sage-devel] Re: linestyles in matplotlib.pyplot.plot

2012-09-13 Thread Goutam Paul
Dear Jason, Thanks. I would continue the discussion in matplotlib forum. Regards, Goutam. On Thu, Sep 13, 2012 at 3:20 PM, Jason Grout wrote: > On 9/13/12 8:11 AM, Goutam Paul wrote: > >> Can we use the markers as alternatives for linestyles? >> Consider the following in sage: >> >> Suppose I h

[sage-devel] Re: linestyles in matplotlib.pyplot.plot

2012-09-13 Thread Jason Grout
On 9/13/12 8:11 AM, Goutam Paul wrote: Can we use the markers as alternatives for linestyles? Consider the following in sage: Suppose I have defined f(x) for a range already, say by the following: x = np.arange(0,1,0.001) import matplotlib.pyplot as plt plt.plot(x,f(x), color='magenta', lines

[sage-devel] Re: linestyles in matplotlib.pyplot.plot

2012-09-13 Thread Goutam Paul
Can we use the markers as alternatives for linestyles? Consider the following in sage: Suppose I have defined f(x) for a range already, say by the following: x = np.arange(0,1,0.001) import matplotlib.pyplot as plt plt.plot(x,f(x), color='magenta', linestyle='--', linewidth=4, label="$f(x)$")

Re: [sage-devel] Upgrade Sage from 5.2 to 5.3, Error installing package linbox-1.1.6.p11

2012-09-13 Thread Jeroen Demeyer
On 2012-09-13 11:30, Garve Ragnara wrote: > Hi! > > I wanted to upgrade Sage, but it fails to (re)install the linbox package. Upgrading to sage-5.3 is known to be broken, this will be fixed in sage-5.4. -- You received this message because you are subscribed to the Google Groups "sage-devel" gr

[sage-devel] Re: Upgrade Sage from 5.2 to 5.3, Error installing package linbox-1.1.6.p11

2012-09-13 Thread Garve Ragnara
Aw, ok. :( thanks. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http:/

[sage-devel] Re: Upgrade Sage from 5.2 to 5.3, Error installing package linbox-1.1.6.p11

2012-09-13 Thread Dima Pasechnik
On Thursday, 13 September 2012 17:30:16 UTC+8, Garve Ragnara wrote: > > Hi! > > I wanted to upgrade Sage, but it fails to (re)install the linbox package. > might be quicker to install 5.3 from scratch... > The last error lines are > > libtool: link: cannot find the library > `/home/garve/Dow

[sage-devel] Re: Upgrade Sage from 5.2 to 5.3, Error installing package linbox-1.1.6.p11

2012-09-13 Thread Garve Ragnara
Whoops, forget the operating system. It's Fedora 17, 64 bit. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@go

[sage-devel] Upgrade Sage from 5.2 to 5.3, Error installing package linbox-1.1.6.p11

2012-09-13 Thread Garve Ragnara
Hi! I wanted to upgrade Sage, but it fails to (re)install the linbox package. The last error lines are libtool: link: cannot find the library `/home/garve/Downloads/sage-5.1/local/lib/../lib64/libstdc++.la' or unhandled argument `/home/garve/Downloads/sage-5.1/local/lib/../lib64/libstdc++.la'