[Python-Dev] why is mmap a builtin module on windows? (original) (raw)
Ralf Schmitt schmir at gmail.com
Wed Jan 23 09:29:59 CET 2008
- Previous message: [Python-Dev] why is mmap a builtin module on windows?
- Next message: [Python-Dev] why is mmap a builtin module on windows?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Jan 23, 2008 9:01 AM, Christian Heimes <lists at cheimes.de> wrote:
> > What is the reason for mmap being a builtin module?
On Windows lots of modules are linked into the python main dll. The file PC/config.c contains a list of all modules. From the point of the maintainer it's much easier to link the modules into the main dll instead of creating standalone dlls. I also suspect that it's much faster because relocation is slow (see PC/dllbase_nt.txt). Martin or Mark can give you a better answer.
ok
Why do you want to overwrite the existing module instead of using a different name like ralfmmap? import ralfmmap as mmap sys.modules]'mmap'] = mmap
I thought about that (ugly hack) too. I would have to change the imports at a lot of places (and revert the changes when we switch to python 2.6). (whereas on Unix I would only have to do install the new mmap module).
- Ralf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20080123/4fdc6b4a/attachment.htm
- Previous message: [Python-Dev] why is mmap a builtin module on windows?
- Next message: [Python-Dev] why is mmap a builtin module on windows?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]