From 11f24e65899a793e3605cf73f68d1757488824d6 Mon Sep 17 00:00:00 2001 From: "andrew.kuchling" Date: Fri, 4 Aug 2006 20:37:43 +0000 Subject: [PATCH] Typo fixes git-svn-id: http://svn.python.org/projects/python/trunk@51115 6015fed2-1504-0410-9fe1-9d1591cc4771 --- Objects/dictnotes.txt | 2 +- Objects/dictobject.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Objects/dictnotes.txt b/Objects/dictnotes.txt index cb46cb120..b0e59a7f1 100644 --- a/Objects/dictnotes.txt +++ b/Objects/dictnotes.txt @@ -243,7 +243,7 @@ kept just for iteration. Caching Lookups --------------- The idea is to exploit key access patterns by anticipating future lookups -based of previous lookups. +based on previous lookups. The simplest incarnation is to save the most recently accessed entry. This gives optimal performance for use cases where every get is followed diff --git a/Objects/dictobject.c b/Objects/dictobject.c index 705be078f..f3b6b7fda 100644 --- a/Objects/dictobject.c +++ b/Objects/dictobject.c @@ -532,7 +532,7 @@ dictresize(dictobject *mp, Py_ssize_t minused) /* Note that, for historical reasons, PyDict_GetItem() suppresses all errors * that may occur (originally dicts supported only string keys, and exceptions * weren't possible). So, while the original intent was that a NULL return - * meant the key wasn't present, it reality it can mean that, or that an error + * meant the key wasn't present, in reality it can mean that, or that an error * (suppressed) occurred while computing the key's hash, or that some error * (suppressed) occurred when comparing keys in the dict's internal probe * sequence. A nasty example of the latter is when a Python-coded comparison -- 2.11.4.GIT