[Python-ideas] Floating point "closeness" Proposal Outline
chris.barker at noaa.gov
Wed Jan 21 17:13:58 CET 2015
On Tue, Jan 20, 2015 at 8:43 PM, Ron Adam <ron3200 at gmail.com> wrote:
> The more we talk about this, the more I'm beginning to dislike the
> symmetric version.
> We are trading an explicit (first, second) relationship with an implicit
> (smaller, larger) relationship. For Python's general use, I don't like
> that. Sorry. :/
I don't think there's really anything more "implicit" about it. And you
could use the mean of a and b if you wanted it a bit less "implicit". But
your other point is well taken, if you DO have a clearly defined "correct"
value, then that is the one to scale the error on. And it's a good idea to
provide that for those cases.
Care to help me write the PEP ?
Christopher Barker, Ph.D.
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-ideas