(original) (raw)
On Jan 23, 2008 9:01 AM, Christian Heimes <lists@cheimes.de> wrote:
ok
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
On Windows lots of modules are linked into the python main dll. The file>
> What is the reason for mmap being a builtin module?
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