[sage-devel] vtk installation issues

2013-10-05 Thread tate engstrand
Hello, all. I am a student in the chemistry department at St. Cloud State University in Minnesota. I've been attempting to install Mayavi from within Sage for use in QM visualization. I am running 64-bit Ubuntu 12.04 on an HP dv7 laptop. I have successfully built sage 5.11 from source. I've re

[sage-devel] Re: Coercion ticket; link from reference manual to thematic tutorial?

2013-10-05 Thread Simon King
Hi Volker, On 2013-10-05, Volker Braun wrote: > I think that presents again a chicken and egg problem. We build the > reference manual first, and then make its index available (via intersphinx) > to the other doc builders. In order to link back we would have to first > build the tutorial (igno

[sage-devel] Re: Coercion ticket; link from reference manual to thematic tutorial?

2013-10-05 Thread Volker Braun
On Saturday, October 5, 2013 8:44:55 PM UTC+1, Simon King wrote: > Nevertheless, is a link "reference manual -> thematic tutorial" easily > possible? A link "thematic tutorial -> reference manual" is ease, it is > enough to write :meth:`sage.structure.parent.Parent.register_coercion` and > so o

[sage-devel] Re: Coercion ticket; link from reference manual to thematic tutorial?

2013-10-05 Thread Simon King
Hi Volker, On 2013-10-05, Volker Braun wrote: > Use ".. automethod:: _coerce_map_from_" to force docbuild of the underscore > methods that should be in the reference manual. See, for example, > sage.structure.parent.Parent.__init__ Thank you! This is a good idea (and I just see that `_coerce_m

[sage-devel] Re: Coercion ticket; link from reference manual to thematic tutorial?

2013-10-05 Thread Volker Braun
Use ".. automethod:: _coerce_map_from_" to force docbuild of the underscore methods that should be in the reference manual. See, for example, sage.structure.parent.Parent.__init__ On Saturday, October 5, 2013 8:29:24 PM UTC+1, Simon King wrote: > > Hi! > > This post has two purposes, namely

[sage-devel] Coercion ticket; link from reference manual to thematic tutorial?

2013-10-05 Thread Simon King
Hi! This post has two purposes, namely an ad and a question. (1) I'd like to make coercion experts aware of #14711, where we are working on fixing yet another memory leak of the coercion system. Without #14711, sage: for D in xrange(2,2**30): : QuadraticField(-D); : would q

[sage-devel] Re: Trac editor sucks

2013-10-05 Thread Simon King
Hi! I just tested: If I scroll up to see the blob, after the jump has occurred, and then scroll down to continue writing, the next jump is not as severe (I could still see what I type), but there still were jumps after seeing the blob. Best regards, Simon -- You received this message because y

[sage-devel] Re: Trac editor sucks

2013-10-05 Thread Simon King
Hi Peter, hi Volker, Am Samstag, 5. Oktober 2013 19:00:46 UTC+2 schrieb Peter Bruin: > > > I have the same problem from time to time (I use both Firefox and Chrome; > I _think_ it only occurs with Chrome for me). > > Interesting. So, one of us sees the problem with Firefox (I), one of us sees it

[sage-devel] Re: Trac editor sucks

2013-10-05 Thread Peter Bruin
Hello, Or more precisely, I find it extremely annoying that *while* I'm typing > the browser suddenly jumps to a totally unrelated location of the page, > so that I have to choose between typing blindly and "scroll back to the > text window for a few seconds until it jumps off again". > I have

Re: [sage-devel] Re: aut codes patch

2013-10-05 Thread Volker Braun
On Saturday, October 5, 2013 2:03:57 PM UTC+1, David Joyner wrote: > > My vote would be to certainly allow it to be an experimental package. > There isn't really too much need for additional work here, what I'm seeing in the current patch is mostly adequate. A bit more documentation of input/ou

Re: [sage-devel] Re: aut codes patch

2013-10-05 Thread David Joyner
On Sat, Oct 5, 2013 at 3:42 AM, Thomas Feulner wrote: > Thanks for all your help. > > @Volker: You are right, the names are terrible. I will change them. There is > no need to have LinearCode_AutGroupCanLabel in the global namespace. I think > LinearCode should have a member of this type, but I wa

[sage-devel] Re: Trac editor sucks

2013-10-05 Thread Simon King
Hi Volker, On 2013-10-05, Volker Braun wrote: > --=_Part_3_5808035.1380967883303 > Content-Type: text/plain; charset=ISO-8859-1 > > I've never seen this happen, but then I'm using chrome to browse trac. But > I would speculate that this is due to the patchbot coloured blob appearing? > When

[sage-devel] Re: aut codes patch

2013-10-05 Thread Volker Braun
On Saturday, October 5, 2013 8:42:34 AM UTC+1, Thomas Feulner wrote: > @Volker: You are right, the names are terrible. I will change them. There > is no need to have LinearCode_AutGroupCanLabel in the global namespace. I > think LinearCode should have a member of this type, but I was not sure if

[sage-devel] Re: Trac editor sucks

2013-10-05 Thread Volker Braun
I've never seen this happen, but then I'm using chrome to browse trac. But I would speculate that this is due to the patchbot coloured blob appearing? When it happens, do you scroll that far up that you can see it? On Saturday, October 5, 2013 9:06:27 AM UTC+1, Simon King wrote: > > Hi! > > I

[sage-devel] Trac editor sucks

2013-10-05 Thread Simon King
Hi! I don't know if we have control on how the editor of the sage trac server works, but I think the editor currently sucks. Or more precisely, I find it extremely annoying that *while* I'm typing the browser suddenly jumps to a totally unrelated location of the page, so that I have to choose bet

[sage-devel] Re: aut codes patch

2013-10-05 Thread Thomas Feulner
Thanks for all your help. @Volker: You are right, the names are terrible. I will change them. There is no need to have LinearCode_AutGroupCanLabel in the global namespace. I think LinearCode should have a member of this type, but I was not sure if this goes well together with an experimental/o