mirror of https://github.com/python/cpython
Typo fixes
This commit is contained in:
parent
db7b443d8a
commit
0067b5fa2b
|
@ -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
|
||||
|
|
|
@ -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
|
||||
|
|
Loading…
Reference in New Issue