Antoine Pitrou <pit...@free.fr> added the comment:
The problem is that it's a change in semantics. So it definitely can't be
backported to the bugfix branches, nor committed into 3.2 which is in feature
freeze now.
The question is which behaviour is the most expected by users of the module.
I'd say that dup()ing definitely isn't intuitive, and it isn't documented; on
the other hand, at least one of the examples seems to assume the original file
descriptor is untouched when close()ing the mmap object:
with open("hello.txt", "r+b") as f:
# memory-map the file, size 0 means whole file
map = mmap.mmap(f.fileno(), 0)
# read content via standard file methods
print(map.readline()) # prints b"Hello Python!\n"
# read content via slice notation
print(map[:5]) # prints b"Hello"
# update content using slice notation;
# note that new content must have same size
map[6:] = b" world!\n"
# ... and read again using standard file methods
map.seek(0)
print(map.readline()) # prints b"Hello world!\n"
# close the map
map.close()
----------
versions: +Python 3.3 -Python 2.7, Python 3.1, Python 3.2
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue10897>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
