On 2012-03-26 07:25, Simon King wrote:
> On 2012-03-26, Ben Hutz wrote:
>> Traceback (most recent call last):
>> ...
>> RuntimeError: Segmentation fault
>
> Oh, and by the way: What you get is a RuntimeError, not a segmentation
> fault in Sage (apparently Sage only complains about a segmentation
Sounds good. Thanks.
On Mar 26, 1:34 am, Simon King wrote:
> On 2012-03-26, Simon King wrote:
>
> > So, it is a bug, and I am about to open a trac ticket for it.
>
> It ishttp://trac.sagemath.org/sage_trac/ticket/12748
>
> Cheers,
> Simon
--
To post to this group, send an email to sage-devel@g
On 2012-03-26, Simon King wrote:
> So, it is a bug, and I am about to open a trac ticket for it.
It is http://trac.sagemath.org/sage_trac/ticket/12748
Cheers,
Simon
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-dev
On 2012-03-26, Ben Hutz wrote:
> Traceback (most recent call last):
> ...
> RuntimeError: Segmentation fault
Oh, and by the way: What you get is a RuntimeError, not a segmentation
fault in Sage (apparently Sage only complains about a segmentation fault
in the backend of the polynomial computation
Hi Ben,
On 2012-03-26, Ben Hutz wrote:
> R.=PolynomialRing(QQ,order=TermOrder('degrevlex',
> 6) + TermOrder('degrevlex',10))
One could argue that weird things are expected to happen if the term
order simply does not match the number of variables.
However, I'd prefer to see a ValueError being ra
