#17011: fix some old scipy-related weirdness in functions/special.py
-------------------------------------+-------------------------------------
       Reporter:  dimpase            |        Owner:
           Type:  defect             |       Status:  new
       Priority:  minor              |    Milestone:  sage-6.4
      Component:  numerical          |   Resolution:
       Keywords:                     |    Merged in:
        Authors:                     |    Reviewers:
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  u/dimpase/fix_some_old_scipy_related_weirdness_in_function_py|  
b690e984e8c2fe2ed9ae7ff9b0165a1422416360
   Dependencies:                     |     Stopgaps:
-------------------------------------+-------------------------------------
Changes (by dimpase):

 * component:  PLEASE CHANGE => numerical
 * priority:  major => minor
 * commit:   => b690e984e8c2fe2ed9ae7ff9b0165a1422416360
 * type:  PLEASE CHANGE => defect


Old description:



New description:

 In couple of places the conversion from scipy complex number to Sage is
 done via strings, which is probably some old relic going back to 2008 or
 so.

 As well, the type of the returned number is default Sage's data, rather
 than C/RDF, as it should be, to avoid confusion about precision of these
 computations, cf e.g. http://ask.sagemath.org/question/24163/why-does-
 sage-offer-unusable-scipy

--

--
Ticket URL: <http://trac.sagemath.org/ticket/17011#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/d/optout.

Reply via email to