Am 24.10.10 20:30, schrieb Pablo De Napoli:
>> have you tried running "sage -docbuild es/tutorial html" ?
>>
> Yes, but I've got the message
>
> 'es/tutorial' is not a recognized document. Type 'sage -docbuild -D' for a
> list
> of documents, or 'sage -docbuild --help' for more help.
>
> it seems
I've succeded in solving this problem: the new language (es) needs to be
added to the global variable LANGUAGES
in doc/common/builder.py
many thanks
Pablo
On Sun, Oct 24, 2010 at 3:30 PM, Pablo De Napoli wrote:
>>
>> have you tried running "sage -docbuild es/tutorial html" ?
>>
>
> Yes, but I've
>
> have you tried running "sage -docbuild es/tutorial html" ?
>
Yes, but I've got the message
'es/tutorial' is not a recognized document. Type 'sage -docbuild -D' for a list
of documents, or 'sage -docbuild --help' for more help.
it seems like this directory es/tutorial needs to be added to som
On Oct 24, 9:08 am, Simon King wrote:
> My impression is that a big change in the category framework,
> infiltrating many parts of Sage, should be discussed here. Do people
> think that a gain in flexibility provided by my additions to the
> category framework would justify a performance loss of 1
Am 24.10.10 17:48, schrieb Pablo De Napoli:
> Hi
>
> I've seen the video "contributing to Sage" where W. Stein mentioned
> the translation of the tutorial to Spanish as
> a possible contribution to sage.
> Indeed, some parts of the tutorial have been already translated into
> Spanish by Luis V. (12
Hi!
Before I open a ticket, I'd like to get some feedback.
My experimental extension of the category framework can do the
following:
1)
It detects containment in categories even if the category has not been
initialised:
sage: P. = QQ['x'][]
sage: P.Element = type(a)
sage: PC_orig = type(P)
sage:
Hi
I've seen the video "contributing to Sage" where W. Stein mentioned
the translation of the tutorial to Spanish as
a possible contribution to sage.
Indeed, some parts of the tutorial have been already translated into
Spanish by Luis V. (12 months ago) However, the translations are
disseminated a
On 2010-10-24 16:07, Jan Groenewald wrote:
> Does SAGE_DEBUG=yes lower -O3 to -O2?
Actually, -O0
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at h
On 10/24/10 02:55 PM, Dan Drake wrote:
On Sun, 24 Oct 2010 at 08:52AM +0100, David Kirkby wrote:
It used to take about 1800 seconds to doctest Sage on my Sun Ultra 27
which runs OpenSolaris. That has now dropped to about 1600 seconds in
the latest version (4.6.rc0).
You can use "sage -coverage
Hi
On Fri, Oct 22, 2010 at 05:30:35PM -0500, Mitesh Patel wrote:
> Would it help to try again with a PARI compiled with less aggressive
> optimizations than our default -O3? For example,
>
> env SAGE_DEBUG=yes ./sage -f pari-2.3.5.p4.spkg
> dmesg | grep segfault | wc -l
> ./sage -t devel/sage/sa
On Sun, 24 Oct 2010 at 08:52AM +0100, David Kirkby wrote:
> It used to take about 1800 seconds to doctest Sage on my Sun Ultra 27
> which runs OpenSolaris. That has now dropped to about 1600 seconds in
> the latest version (4.6.rc0).
You can use "sage -coverageall" to give you information on the n
It used to take about 1800 seconds to doctest Sage on my Sun Ultra 27
which runs OpenSolaris. That has now dropped to about 1600 seconds in
the latest version (4.6.rc0).
I've not upgraded the hardware, compiler or other software, so I can't
understand why it should now to take less time to doctest
12 matches
Mail list logo
