Issue #11141: Fix the shelve documentation to use a list, not a range object.

Patch by SilentGhost.

diff --git a/Doc/ACKS.txt b/Doc/ACKS.txt
index bcf70b5ecb4ea3e8b303ff02127b6dd2cb5d5925..c51d211180e694c816787a992467fa98a7302c8a 100644 (file)
--- a/Doc/ACKS.txt
+++ b/Doc/ACKS.txt
@@ -182,6 +182,7 @@ docs@python.org), and we'll be glad to correct the problem.
    * Joakim Sernbrant
    * Justin Sheehy
    * Charlie Shepherd
+   * SilentGhost
    * Michael Simcich
    * Ionel Simionescu
    * Michael Sloan

diff --git a/Doc/library/shelve.rst b/Doc/library/shelve.rst
index 4b49a2f006b7ca210514b3f192e7051d63126673..9d7d5045e2031626b9e3ef0319bc66ba22a18dfc 100644 (file)
--- a/Doc/library/shelve.rst
+++ b/Doc/library/shelve.rst
@@ -169,8 +169,8 @@ object)::
    klist = list(d.keys()) # a list of all existing keys (slow!)
 
    # as d was opened WITHOUT writeback=True, beware:
-   d['xx'] = range(4)  # this works as expected, but...
-   d['xx'].append(5)   # *this doesn't!* -- d['xx'] is STILL range(4)!
+   d['xx'] = [0, 1, 2]    # this works as expected, but...
+   d['xx'].append(3)      # *this doesn't!* -- d['xx'] is STILL [0, 1, 2]!
 
    # having opened d without writeback=True, you need to code carefully:
    temp = d['xx']      # extracts the copy