Carl Banks wrote: > Frankly, I'm not so sure matching Windows behavior is a great idea. > mmap module seems to be having an identity crisis. Is it a low-level > system call, or a high-level, OS-independent way to access files as > blocks of memory? The modules is moving towards the latter (what with > Unix mmap accepting ACCESS-style flags, and now this file-resizing > behavior). I actually favor a two-level approach similar to file I/O: > there would low-level system calls in the os module, and high-level > mmap object. (The high-level object would go all the way. It would > accept a filename rather than a file descriptor, anonymous blocks would > be handled OS-independently, rather than mapping /dev/zero, and so on.)
I'm sure that we will gladly accept a patch implementing this approach. Cheers, Georg -- http://mail.python.org/mailman/listinfo/python-list
