Hello,
I was suggesting it for inclusion in Sage, both to ease the transition
to Python 3 and to make its behaviour more appropriate for a CAS.
However, as some users have pointed out, it does not maintain
precision, and it is still used by some for floor division. Perhaps it
is not yet ready.
--
On Fri, 21 Jan 2011 at 01:29AM +0100, Sébastien Labbé wrote:
> Personally, I gave a talk on How to contribute to Sage in 22 easy
> steps! [2] and thought it might be a good idea to share it on this
> list.
Thanks for sharing that! It's a really nice presentation.
> Although most of the participan
In my case abort() will happen for potentially many different reasons.
So I'd like to have
#include "c_lib/include/interrupt.h"
char[1000] errmessage
void libgap_errors()
{
set_sage_signal_handler_message(errmessage);
abort();
}
and set errmessage in the Cython code.
Will this work?
Salut Pablo,
I dont know if it can help but this week I found this makefile which
helped me to understand how to call sphinx with which options :
devel/sage-main/doc/en/tutorial/Makefile
Sébastien
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this g
Hi sage-devel,
Sage Days 28 [1] ended yesterday after three very good days. Many
tutorials were given (all links are on the wiki page). Personally, I
gave a talk on How to contribute to Sage in 22 easy steps! [2] and
thought it might be a good idea to share it on this list. Although
most of the pa
On Jan 20, 8:56 pm, Jeroen Demeyer wrote:
> On 2011-01-20 21:52, Robert Miller wrote:
>
> > This file (hgrc) should be removed. It must have ended up there while
> > I was release managing sage-4.1, although how it ended up there I have
> > no idea.
>
> Please review #10663.
I Removed it and now
On 2011-01-20 21:52, Robert Miller wrote:
> This file (hgrc) should be removed. It must have ended up there while
> I was release managing sage-4.1, although how it ended up there I have
> no idea.
Please review #10663.
--
To post to this group, send an email to sage-devel@googlegroups.com
To un
This file (hgrc) should be removed. It must have ended up there while
I was release managing sage-4.1, although how it ended up there I have
no idea.
On Thu, Jan 20, 2011 at 11:13 AM, Emil Widmann wrote:
> I compiled 4.6.1 and did "make ptestlong"
>
> All tests passed but one:
>
> sage -t -long
I compiled 4.6.1 and did "make ptestlong"
All tests passed but one:
sage -t -long -force_lib devel/sage/sage/tests/cmdline.py
**
File "/initrd/mnt/dev_save/sage-4.6.1/devel/sage-main/sage/tests/
cmdline.py", line 283:
sage:
Em 19 de janeiro de 2011 14:57, Paulo César Pereira de Andrade
escreveu:
> Em 18 de janeiro de 2011 14:55, Paulo César Pereira de Andrade
> escreveu:
>> Hi,
>>
>> I made a patch that allowed it to generate documentation and build, but
>> it just gives the same errors when attempting to execute
Looking at your install.log, it is libpng which failed:
make[3]: Leaving directory
`/home/drake/mark/sage-4.6.2.alpha1/spkg/build/libpng-1.2.35.p2/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/home/drake/mark/sage-4.6.2.alpha1/spkg/build/libpng-1.2.35.p2/src'
Error building libpng
The current way of dealing with this is to abort() in the C library,
which will raise RuntimeError inside sig_on()/sig_off(). Something like::
#include "c_lib/include/interrupt.h"
void libgap_division_by_zero()
{
set_sage_signal_handler_message("GAP: Division by zero");
abort();
}
Then i
On Jan 20, 8:45 pm, Jeroen Demeyer wrote:
> On 2011-01-20 10:37, Dima Pasechnik wrote:
>
> > Hoi Jeroen,
> > do you have an example with the new syntax of the situation that I
> > describe?
something like:
cdef class GapElement(RingElement):
# include setjmp C header
cdef static
On 2011-01-20 10:37, Dima Pasechnik wrote:
> Hoi Jeroen,
> do you have an example with the new syntax of the situation that I
> describe?
It is not really clear to me what you want to do. But I certainly want
to help doing whatever it is you want to do.
--
To post to this group, send an email t
On 20 January 2011 09:43, Florent Hivert wrote:
> On Thu, Jan 20, 2011 at 09:37:26AM +, John Cremona wrote:
>> On 20 January 2011 09:31, Florent Hivert
>> wrote:
>>
>> >>
>> >> OK, that's easy -- just add it in sage/misc/latex_macros.py in the
>> >> obvious place where there's a list of simi
On Thu, Jan 20, 2011 at 09:37:26AM +, John Cremona wrote:
> On 20 January 2011 09:31, Florent Hivert wrote:
>
> >>
> >> OK, that's easy -- just add it in sage/misc/latex_macros.py in the
> >> obvious place where there's a list of similar things. A simple patch!
> >
> > Sure ! My question isn
On 20 January 2011 09:31, Florent Hivert wrote:
>>
>> OK, that's easy -- just add it in sage/misc/latex_macros.py in the
>> obvious place where there's a list of similar things. A simple patch!
>
> Sure ! My question isn't technical. Sorry for not being clear about it. The
> list of those macros
Hoi Jeroen,
do you have an example with the new syntax of the situation that I
describe?
(setjmp in Cython)
Thanks,
Dima
On Jan 20, 4:53 pm, Jeroen Demeyer wrote:
> On 2011-01-20 05:03, Dima Pasechnik wrote:
>
> > I wonder if it is possible to use setjmp/longjmp in order to return to
> > a place
On Thu, Jan 20, 2011 at 09:17:49AM +, John Cremona wrote:
> On 20 January 2011 08:51, Florent Hivert wrote:
> > Hi John,
> >
> > On Wed, Jan 19, 2011 at 10:45:05PM +, John Cremona wrote:
> >> What more than the following are you proposing?
> >>
> >> sage: version()
> >> 'Sage Version
On 20 January 2011 08:51, Florent Hivert wrote:
> Hi John,
>
> On Wed, Jan 19, 2011 at 10:45:05PM +, John Cremona wrote:
>> What more than the following are you proposing?
>>
>> sage: version()
>> 'Sage Version 4.6.2.alpha0, Release Date: 2011-01-13'
>> sage: NN
>> Non negative integer se
On 2011-01-20 05:03, Dima Pasechnik wrote:
> I wonder if it is possible to use setjmp/longjmp in order to return to
> a place in a Cython function (within Sage) from a dynamically loaded
> library written in C.
> (this would be a way to handle exceptions in GAP interpreter in libGAP
> (see #6391))
Hi John,
On Wed, Jan 19, 2011 at 10:45:05PM +, John Cremona wrote:
> What more than the following are you proposing?
>
> sage: version()
> 'Sage Version 4.6.2.alpha0, Release Date: 2011-01-13'
> sage: NN
> Non negative integer semiring
> sage: latex(NN)
> \Bold{N}
When I wrote my e-mai
Hello:
I'm working on two issues [1], [2] that require me to mess up with
sphinx. Anybody has any tips about the right place to interfere the
building of the documentation? I would need to define extra codes like:
..link_all::
to tell the testing framework to link all code cells (this means
v
23 matches
Mail list logo
