Chris, Could you please add a link to the email where the PEP was accepted? Thanks, Yury On 2015-05-16 10:12 PM, chris.angelico wrote: > https://hg.python.org/peps/rev/f876276ce076 > changeset: 5854:f876276ce076 > user: Chris Angelico <rosuav at gmail.com> > date: Sun May 17 12:12:19 2015 +1000 > summary: > Apply Chris's changes, including an acceptance mark > > files: > pep-0485.txt | 6 +++--- > 1 files changed, 3 insertions(+), 3 deletions(-) > > > diff --git a/pep-0485.txt b/pep-0485.txt > --- a/pep-0485.txt > +++ b/pep-0485.txt > @@ -3,7 +3,7 @@ > Version: $Revision$ > Last-Modified: $Date$ > Author: Christopher Barker <Chris.Barker at noaa.gov> > -Status: Draft > +Status: Accepted > Type: Standards Track > Content-Type: text/x-rst > Created: 20-Jan-2015 > @@ -391,9 +391,9 @@ > The most common use case is expected to be small tolerances -- on order of the > default 1e-9. However there may be use cases where a user wants to know if two > fairly disparate values are within a particular range of each other: "is a > -within 200% (rel_tol = 2.0) of b? In this case, the string test would never > +within 200% (rel_tol = 2.0) of b? In this case, the strong test would never > indicate that two values are within that range of each other if one of them is > -zero. The strong case, however would use the larger (non-zero) value for the > +zero. The weak case, however would use the larger (non-zero) value for the > test, and thus return true if one value is zero. For example: is 0 within 200% > of 10? 200% of ten is 20, so the range within 200% of ten is -10 to +30. Zero > falls within that range, so it will return True. > > > > _______________________________________________ > Python-checkins mailing list > Python-checkins at python.org > https://mail.python.org/mailman/listinfo/python-checkins
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4