[sage-combinat-devel] Installing combinat queue

2013-06-28 Thread Andrew Mathas
Hi All, Whenever I try installing the combinat queue on top of a new verion tehse days I run into an error like this: MacAndrew-528-(sage-5.10)-combinat: sage -combinat install Creating sage-combinat branch: /usr/local/src/sage/sage-5.10/sage -b main

[sage-combinat-devel] Re: Installing combinat queue

2013-06-28 Thread Travis Scrimshaw
Hey Andrew, Are you compiling it from source code or using the prebuilt? Because I believe building the doc is built during the compilation. As for the prebuilts, since sage now copies over the doc (previously it just rebuilt it) and it may not be included in; so look in your

[sage-combinat-devel] docstrings and overloaded methods

2013-06-28 Thread Darij Grinberg
Hi, here's a quick question: I'm defining some method on a class and then redefining it on a subclass for speed improvement. (Concretely, it is a map on the symmetric functions which I redefine on the power-sum basis because it's easier to compute there.) What should I do with the docstring?

Re: [sage-combinat-devel] Re: docstrings and overloaded methods

2013-06-28 Thread Darij Grinberg
Hi Simon, thanks -- but the doctests are the least of my worries (I was going to do what you suggested). I am trying to figure out what to do with the docstring text that explains what the function does. If I don't copypaste it, then calling ?? on the function won't always return the text. If I

[sage-combinat-devel] Re: docstrings and overloaded methods

2013-06-28 Thread Simon King
Hi Darij, On 2013-06-28, Darij Grinberg darijgrinb...@gmail.com wrote: here's a quick question: I'm defining some method on a class and then redefining it on a subclass for speed improvement. (Concretely, it is a map on the symmetric functions which I redefine on the power-sum basis because

Re: [sage-combinat-devel] Re: docstrings and overloaded methods

2013-06-28 Thread Travis Scrimshaw
Hey Darij, My belief/viewpoint is that the one-line will likely be about the same since it is suppose to be a concise summery, and the more detailed description can be linked to one abstract/base function by using :meth:`SuperClass.foo`. I'd also suspect I'm somewhat in the minority here