Path: csiph.com!usenet.pasdenom.info!dedibox.gegeweb.org!gegeweb.eu!nntpfeed.proxad.net!proxad.net!feeder1-2.proxad.net!usenet-fr.net!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.007 X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'line:': 0.07; 'subject:question': 0.08; 'closest': 0.09; 'subject:()': 0.09; ':-p': 0.16; 'ah,': 0.16; 'from:addr:mrabarnett.plus.com': 0.16; 'from:addr:python': 0.16; 'from:name:mrab': 0.16; 'message- id:@mrabarnett.plus.com': 0.16; 'nearest': 0.16; 'received:84.93': 0.16; 'received:84.93.230': 0.16; 'subject:API': 0.16; 'wrote:': 0.17; "shouldn't": 0.17; 'tim': 0.18; 'exists.': 0.22; "i'd": 0.22; 'header:In-Reply-To:1': 0.25; 'header:User-Agent:1': 0.26; 'question': 0.27; 'chase': 0.29; 'received:192.168.1.3': 0.29; 'error': 0.30; 'received:84': 0.32; 'raising': 0.33; 'to:addr :python-list': 0.33; 'should': 0.36; 'subject:: ': 0.38; 'instead': 0.39; 'to:addr:python.org': 0.39; 'received:192': 0.39; 'where': 0.40; 'received:192.168': 0.40; 'skip:n 10': 0.63; 'header:Reply-To:1': 0.68; 'reply-to:no real name:2**0': 0.72; 'furman': 0.84; 'reply-to:addr:python.org': 0.84; 'ethan': 0.91 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.0 cv=IekFqBWa c=1 sm=1 a=0nF1XD0wxitMEM03M9B4ZQ==:17 a=DKcI9XZsuF4A:10 a=xb2YPhB8IJoA:10 a=ihvODaAuJD4A:10 a=OUOv7kDek9cA:10 a=8nJEP1OIZ-IA:10 a=EBOSESyhAAAA:8 a=8AHkEIZyAAAA:8 a=sUy49W4grkkA:10 a=Kt3aKh5QF9_rT5Rl7l8A:9 a=wPNLvfGTeEIA:10 a=0nF1XD0wxitMEM03M9B4ZQ==:117 X-AUTH: mrabarnett:2500 Date: Thu, 16 Aug 2012 03:20:04 +0100 From: MRAB User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: python-list@python.org Subject: Re: dbf.py API question concerning Index.index_search() References: <502C3011.7070103@stoneleaf.us> <502C3304.70805@tim.thechases.com> <502C3CFB.8080504@stoneleaf.us> <502C3EAF.5050802@tim.thechases.com> In-Reply-To: <502C3EAF.5050802@tim.thechases.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: python-list@python.org List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 19 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1345083600 news.xs4all.nl 6867 [2001:888:2000:d::a6]:39002 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:27135 On 16/08/2012 01:28, Tim Chase wrote: > On 08/15/12 19:21, Ethan Furman wrote: >> The well-hidden clue was this line: >> >> nearest returns where the match should be instead of raising an error >> >> And my question should have been: >> >> What should the return value be when nearest == True? > > Ah, well that's somewhat clearer. Return the closest and not bother > to let the user know it was inexact. Upon requesting it with > nearest=True, they *knew* that the result might be a nearest match. > Though if they ask for nearest, an exact match *better* be the > nearest if it exists. :-P > > I'd say the API-user shouldn't ask for what they don't want. > +1