Re: [sage-devel] Re: sage 5.6.beta1 build error (mercurial-2.2.2.p0) on OS X 10.8.2

2013-02-03 Thread Neal Harris
I'm not sure if this has been reported already, but I just had an error while trying to build Sage 5.6 on 10.8.2: In file included from /System/Library/Frameworks/CoreGraphics.framework/Headers/CGDisplayStream.h:11:0, from /System/Library/Frameworks/CoreGraphics.framework/Heade

[sage-devel] Re: Messing up hash and cmp with UniqueRepresentation

2013-02-03 Thread Simon King
Hi, On 2013-01-30, Simon King wrote: > Another patch, that cythons UniqueRepresentation and seems to > drastically improve the performance of using UniqueRepresentation > instances as dictionary keys, will soon be ready. The patch is now posted at #14054. About performance: For example, the tim

[sage-devel] Re: Cached method bug ?

2013-02-03 Thread Nils Bruin
On Feb 3, 1:37 am, Nils Bruin wrote: > See line 1807 for sage/misc/cachefunc.pyx: Actually, I'm not so sure that code ever gets executed in our example. I certainly didn't get any results from putting "raise" or "print" commands there. On class level, there's the CachedMethod that is supposed to

[sage-devel] Some Old Tickets

2013-02-03 Thread Kannappan Sampath
Hello friends, I would like to bring to people's notice the following: we have a couple of jsMath related tickets. That we have shifted over to MathJaX for the notebook interface, are these at all relevant? Some of the meta things -- yes, but specifics about jsMath, may not be. Should we clear the

Re: [sage-devel] Re: Sage live USB (Debian based, with self-replicating capabilities)

2013-02-03 Thread Thierry
Hi, On Fri, Feb 01, 2013 at 03:38:22PM -0600, Jason Grout wrote: > On 1/7/13 11:09 AM, sage-googlesu...@lma.metelu.net wrote: > >here is a link to the self-replicating live USB we discussed about in the > >Bobo > >2012 sage days thread. > > > >http://sagedebianlive.metelu.net/ > > > I just down

[sage-devel] Re: Cached method bug ?

2013-02-03 Thread Simon King
Hi Nils, On 2013-02-03, Nils Bruin wrote: > The next time around, this shouldn't happen anymore! indeed, > "setattr(inst,self.__name__, Caller)" seems to try and fix that. But > that won't make > "return (inst.__cached_methods).__getitem__(self.__name__)" > succeed next time around! shouldn't it

[sage-devel] Too long lines cut off in the pdf documentation

2013-02-03 Thread mbejger
Dear group, First-time poster here :-) Is there a systematic way to deal with too long lines that doesn't involve manual corrections? Any help would be appreciated ;-) There was a topic about it in 2008, but now it seems obsolete https://groups.google.com/forum/?fromgroups=#!topic/sage-devel/

[sage-devel] Re: Sage live USB (Debian based, with self-replicating capabilities)

2013-02-03 Thread Sébastien Labbé
> I'm curious: would something like these instructions work? > > (I'll probably try seeing if I can follow them, but I don't know too > much about the problems right now.) Well, for me at least, running osx 10.5.8, I was not able to make the USB appear in the "Startup Manager" as explained he

[sage-devel] Re: Cached method bug ?

2013-02-03 Thread Nils Bruin
I think the problem is in CachedMethodCallerNoArgs.__get__, which is the function responsible for retrieving the cached function instance from the class or its instance. See line 1807 for sage/misc/ cachefunc.pyx: try: return (inst.__cached_methods).__getitem__(self.__name__)

[sage-devel] Re: Cached method bug ?

2013-02-03 Thread Simon King
Hi Nils, On 2013-02-02, Nils Bruin wrote: > OK, I tried reading the code and I decided that I don't understand > what it IS doing. You wrote it so you might know better :-). At least, I have no idea why accessing the attribute f.trac.cache makes f.truc.cache vanish, even though f.trac.cache is f