Also fun: The git man-page
generator http://git-man-page-generator.lokaltog.net/
On Saturday, October 31, 2015 at 4:00:39 AM UTC+1, kcrisman wrote:
>
> http://xkcd.com/1597/
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from
Hi
This might be a leftover error from a previous versio nwhen mathjax moved.
Please try
sudo -i
cd
/usr/lib/sagemath/local/lib/python2.7/site-packages/sagenb-0.11.4-py2.7.egg/sagenb/data/
rm -rf mathjax
ln -s ../../../../../../share/mathjax/
Or inspect first whether that symlink is there alread
Hi Sage Developers,
Who is interested in a Sage Days adjacent to the Joint Math Meetings
in January 2016 in Seattle? I have funding for US citizens. And I
live in Seattle.
-- William
--
William (http://wstein.org)
--
You received this message because you are subscribed to the Google Groups
> Maybe we really do, since I can remember a number of tickets where tests
> were removed or changed from the most useful versions because even the
> "long" tests were running more than X seconds in the file (for a smallish
> value of X, not 3600 or something). Then at least one could run the real
Hi all
I already sent this to sage-nt but didn't get a response, so I try
again: Can someone maybe have a look at one of the tickets above
(in particular #17909)?
They are for modular forms for Hecke triangle groups.
In particular this includes (classical) modular forms for SL2(Z)
and for the
On Mon, 2 Nov 2015, kcrisman wrote:
If you have tests that take too long, then we need another tag "#
really long".
Maybe we really do, since I can remember a number of tickets where tests
were removed or changed from the most useful versions because even the
"long" tests were running more t
>
>
> >> That's what
> >>
> >> # long time
> >>
> >> is supposed to be for.
> >
> > I don't think so. You wouldn't want to see a doctest take one hour to
> > run, even if it is flagged with 'long time'. I don't know about you,
> > but I run 'long' doctests several time per day on some
Unfortunately I'm unable to help with this. It looks like a Sage/toolchain
issue which I'm afraid someone else will have to sort out. I don't have any
ideas at all.
Bill.
On Sunday, 1 November 2015 21:31:39 UTC+1, pang wrote:
>
> mpir 2.7.0 compiled just fine using the AUR package. I didn't 'pa
On 2015-10-30 08:35, Jori Mäntysalo wrote:
- Be better developer with sort(result) or something similar
This option has my vote because it's the most explicit. We shouldn't
allow the doctest framework to behave too much different from an
interactive session, so I'm not in favour of behind-the
