diff options
| author | Tim Peters <tim.peters@gmail.com> | 2006-04-11 01:47:17 +0000 |
|---|---|---|
| committer | Tim Peters <tim.peters@gmail.com> | 2006-04-11 01:47:17 +0000 |
| commit | 527f652a8f0feaa8fba4b2d3f746dde6ebb55ce8 (patch) | |
| tree | fe265bb9d6d639cc192d5b12e9853727103b0eae | |
| parent | 413c9226d27a09526b0edbe58317426ea1df83a3 (diff) | |
| download | cpython-git-527f652a8f0feaa8fba4b2d3f746dde6ebb55ce8.tar.gz | |
Typo repair.
| -rw-r--r-- | Misc/NEWS | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -15,7 +15,7 @@ Core and builtins - Patch #837242: ``id()`` of any Python object always gives a positive number now, which might be a long integer. ``PyLong_FromVoidPtr`` and ``PyLong_AsVoidPtr`` have been changed accordingly. Note that it has - never been correct to implement a ``hash()`` method that returns the + never been correct to implement a ``__hash()__`` method that returns the ``id()`` of an object: def __hash__(self): @@ -23,7 +23,7 @@ Core and builtins because a hash result must be a (short) Python int but it was always possible for ``id()`` to return a Python long. However, because ``id()`` - cuold return negative values before, on a 32-bit box an ``id()`` result + could return negative values before, on a 32-bit box an ``id()`` result was always usable as a hash value before this patch. That's no longer necessarily so. |