#20261: Conversion of 0 in cyclotomic field fails
------------------------------+------------------------
Reporter: fstromberg | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-7.3
Component: coercion | Resolution:
Keywords: cyclotomic | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
------------------------------+------------------------
Changes (by vdelecroix):
* milestone: sage-7.2 => sage-7.3
Old description:
> In some cases the element 0 of one cyclotomic field cannot be coerced
> properly to 0
> in another cyclotomic field. For instance in Sage 7.1 and Sage 7.2.rc1:
> {{{
> sage: K12 = CyclotomicField(12)
> sage: K6 = CyclotomicField(6)
> sage: K12(K6(0))
> 0
> sage: K6(K12(0))
> Traceback (most recent call last)
> ...
> TypeError: unable to coerce <class 'sage.rings.infinity.PlusInfinity'> to
> an integer
> }}}
New description:
In some cases the element 0 of one cyclotomic field cannot be converted
properly to 0
in another cyclotomic field. For instance in Sage 7.1 and Sage 7.2.rc1:
{{{
sage: K12 = CyclotomicField(12)
sage: K6 = CyclotomicField(6)
sage: K12(K6(0)) # coercion K6 -> K12 is fine
0
sage: K6(K12(0)) # partial conversion K12 -> K6 is not
Traceback (most recent call last)
...
TypeError: unable to coerce <class 'sage.rings.infinity.PlusInfinity'> to
an integer
}}}
--
Comment:
Indeed, I did not have a look at the title!
--
Ticket URL: <http://trac.sagemath.org/ticket/20261#comment:6>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
