#12967: bugs in comparisons between constants, wrapped pyobjects, infinity
-------------------------------------+-------------------------------------
Reporter: dkrenn | Owner: burcin
Type: defect | Status: needs_work
Priority: major | Milestone: sage-6.6
Component: symbolics | Resolution:
Keywords: compare pi | Merged in:
infinity bool | Reviewers: Karl-Dieter Crisman
Authors: Travis Scrimshaw, | Work issues:
Ralf Stephan | Commit:
Report Upstream: N/A | c5845f6b18d582807dafaaf60ad6a5c8017173f3
Branch: u/rws/12967-2 | Stopgaps:
Dependencies: #17984 |
-------------------------------------+-------------------------------------
Comment (by pbruin):
Replying to [comment:38 rws]:
> Replying to [comment:35 pbruin]:
> >...the strategy to implement `x in P` as `bool(P(x) == x)` basically
seems a good one to me.
> It would be if users wanted `x in RR/CC` to mean `x element of
real/complex field of exactly this precision` but the overwhelming
majority want it to mean `x element of real/complex field regardless of
precision`. And that's also the use cases within Sage that I have seen,
and so I reflected it in the method description.
But currently the precision is already taken care of in this way:
{{{
sage: pi.n(10) in RR
True
sage: pi.n(100) in RealField(50)
True
}}}
Isn't this what you want to keep as the correct behaviour?
--
Ticket URL: <http://trac.sagemath.org/ticket/12967#comment:39>
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.
