[kupfer] relevance: Use s.find() directly instead of _index
- From: Ulrik Sverdrup <usverdrup src gnome org>
- To: svn-commits-list gnome org
- Cc:
- Subject: [kupfer] relevance: Use s.find() directly instead of _index
- Date: Fri, 11 Sep 2009 18:50:20 +0000 (UTC)
commit 9a25f12228560bc13a844df2887e4f31689fe942
Author: Ulrik Sverdrup <ulrik sverdrup gmail com>
Date: Fri Sep 11 20:04:28 2009 +0200
relevance: Use s.find() directly instead of _index
Test shows that we gain exactly nothing. So it seems.
kupfer/relevance.py | 5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
---
diff --git a/kupfer/relevance.py b/kupfer/relevance.py
index 3381676..852553a 100644
--- a/kupfer/relevance.py
+++ b/kupfer/relevance.py
@@ -197,8 +197,7 @@ def _findBestMatch(s, query):
return bestMatch
# Loop through each instance of the first character in query
- _index = s.find
- index = _index(query[0])
+ index = s.find(query[0])
queryLength = len(query)
lastIndex = lastChar - len(query) + 1
@@ -218,7 +217,7 @@ def _findBestMatch(s, query):
else:
break
- index = _index(query[0], index + 1)
+ index = s.find(query[0], index + 1)
return bestMatch
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]