#15695: Coercion problems between numpy and sage floats
-------------------------------------+-------------------------------------
Reporter: nbruin | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.1
Component: coercion | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/nbruin/ticket/15695 | f07008bd6f1e9b5a37a4d3eae874a5eac2815234
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Changes (by nbruin):
* commit: => f07008bd6f1e9b5a37a4d3eae874a5eac2815234
Comment:
very basic fix. Feel free to adapt. Don't forget to test (including
performance regression. Python should be able to do a `issubtype` really
quickly, but it will be slower than an identity test)
----
New commits:
||[http://git.sagemath.org/sage.git/commit/?id=f07008bd6f1e9b5a37a4d3eae874a5eac2815234
f07008b]||{{{trac #15695: check for subtypes in py_scalar_type}}}||
--
Ticket URL: <http://trac.sagemath.org/ticket/15695#comment:2>
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.
For more options, visit https://groups.google.com/groups/opt_out.
