From: Senthil Kumaran <senthil@uthcode.com>
Date: Tue, 10 Sep 2013 05:39:28 +0000 (-0700)
Subject: Clarify mmap.close method  behavior.  Addresses issue  #18815
X-Git-Tag: v3.4.0a3~88^2
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=b9183950d80b42cf7d37a82f5a58e5561355e177;p=python

Clarify mmap.close method  behavior.  Addresses issue  #18815
Patch contributed by Anoop Thomas Mathew.
---

diff --git a/Doc/library/mmap.rst b/Doc/library/mmap.rst
index 1f36cecec2..7db60d24f8 100644
--- a/Doc/library/mmap.rst
+++ b/Doc/library/mmap.rst
@@ -155,8 +155,9 @@ To map anonymous memory, -1 should be passed as the fileno along with the length
 
    .. method:: close()
 
-      Close the file.  Subsequent calls to other methods of the object will
-      result in an exception being raised.
+      Closes the mmap. Subsequent calls to other methods of the object will
+      result in a ValueError exception being raised. This will not close
+      the open file.
 
 
    .. attribute:: closed