Hi,
On 22 Okt., 16:20, "John Cremona" <[EMAIL PROTECTED]> wrote:
> 2008/10/22 Robert Bradshaw <[EMAIL PROTECTED]>:
>
>
>
>
>
> > On Oct 22, 2008, at 5:51 AM, John Cremona wrote:
>
> >> 2008/10/22 mabshoff <[EMAIL PROTECTED]>:
>
> >>> On Oct 22, 5:14 am, "John Cremona" <[EMAIL PROTECTED]> wrote:
>
2008/10/22 Robert Bradshaw <[EMAIL PROTECTED]>:
>
> On Oct 22, 2008, at 5:51 AM, John Cremona wrote:
>
>> 2008/10/22 mabshoff <[EMAIL PROTECTED]>:
>>>
>>>
>>>
>>> On Oct 22, 5:14 am, "John Cremona" <[EMAIL PROTECTED]> wrote:
While working on #3318 I cam across a really terrible bug introduced
On Oct 22, 2008, at 5:51 AM, John Cremona wrote:
> 2008/10/22 mabshoff <[EMAIL PROTECTED]>:
>>
>>
>>
>> On Oct 22, 5:14 am, "John Cremona" <[EMAIL PROTECTED]> wrote:
>>> While working on #3318 I cam across a really terrible bug introduced
>>> between 3.1.4 and 3.2.alpha0 in the file sage/rings/in
2008/10/22 mabshoff <[EMAIL PROTECTED]>:
>
>
>
> On Oct 22, 5:14 am, "John Cremona" <[EMAIL PROTECTED]> wrote:
>> While working on #3318 I cam across a really terrible bug introduced
>> between 3.1.4 and 3.2.alpha0 in the file sage/rings/integer.pyx which
>> produces the following terrible thing:
On Oct 22, 5:14 am, "John Cremona" <[EMAIL PROTECTED]> wrote:
> While working on #3318 I cam across a really terrible bug introduced
> between 3.1.4 and 3.2.alpha0 in the file sage/rings/integer.pyx which
> produces the following terrible thing:
>
> --