[sage-devel] Re: Inconsistencies in comparing

2017-05-03 Thread Marc Mezzarobba
Ralf Stephan wrote: > Do I understand it right that then I can coerce a real to a complex > ball and always back to a real without raising an exception? Coerce, no; convert, yes, I think (assuming that by "a real" you mean "an element of a RealField"), but that's an implementation detail, not so

[sage-devel] Re: Inconsistencies in comparing

2017-05-03 Thread Ralf Stephan
On Wednesday, May 3, 2017 at 2:45:00 PM UTC+2, Marc Mezzarobba wrote: > > (Subsequent *operations* on those elements will be done with a precision > of p, though.) This is convenient in combination with automatic > coercion. Do I understand it right that then I can coerce a real to a complex

[sage-devel] Re: Inconsistencies in comparing

2017-05-03 Thread Frédéric Chapoton
You may have noticed that somebody is painfully trying to make comparison compatible with python3. The semantics of comparison for RealInterval is "every element of A has the given relation to every element of B". This will not change, as many people are saying this is exactly what they want. I

[sage-devel] Re: Inconsistencies in comparing

2017-05-03 Thread Marc Mezzarobba
Hi, Ralf Stephan wrote: > This though seems buggy: > sage: BF = RealBallField(precision=2) > sage: BF(1.002)>BF(1.001) > True > sage: BF(1.002)-BF(1.001) > [+/- 1.20e-7] I don't think there is a bug here. The difference prints as an interval containing zero, but this is a correct