#13957: catch ValueError in comparisons
----------------------------------------+-----------------------------------
Reporter: vdelecroix | Owner: vdelecroix
Type: defect | Status: positive_review
Priority: major | Milestone:
sage-duplicate/invalid/wontfix
Component: coercion | Resolution:
Keywords: coercion, comparison | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
----------------------------------------+-----------------------------------
Changes (by vdelecroix):
* cc: vdelecroix (added)
* status: needs_review => positive_review
* milestone: sage-5.10 => sage-duplicate/invalid/wontfix
* author: Vincent Delecroix =>
Old description:
> When element construction by a parent raise a ValueError, it prevents
> using the coercion in comparisons.
New description:
When element construction by a parent raise a ValueError, it prevents
using the coercion in comparisons.
Note: a coercion should not fail and there is no reason to catch a
ValueError.
--
Comment:
Hi Travis,
I open the ticket because we made some stupid design decisions for #12224.
The point was that we implement a coercion from lists to Words and we
raised some `ValueError` if the content of the list does not match the
alphabet. As I learn, it is definitely not what we want from a coercion: a
coercion should always succeed.
I close it as wont fix.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13957#comment:7>
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 http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
