<br><br><div class="gmail_quote">On Jan 23, 2008 10:12 PM, "Martin v. Löwis" <<a href="mailto:martin@v.loewis.de">martin@v.loewis.de</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">> On Windows lots of modules are linked into the python main dll. The file<br>> PC/config.c contains a list of all modules. From the point of the<br>> maintainer it's much easier to link the modules into the main dll
<br>> instead of creating standalone dlls. I also suspect that it's much<br>> faster because relocation is slow (see PC/dllbase_nt.txt). Martin or<br>> Mark can give you a better answer.<br><br></div>Actually, that *is* the current answer. That plus a remark
<br>"Contributions are welcome, as long as they<br>a) come with a clear, objective policy on what should go into<br>pythonxy.dll and what not, and</blockquote><div><br>I'd say anything that is needed by "import sys, os" is a candidate for being included.
<br>Currently even the _csv module is a builtin module on windows. But then I don't know how much slower importing from a .pyd file is..<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>b) automate all aspects of adding modules that should not go<br>into pythonxy.dll according to the policy."<br></blockquote><div><br>i.e. create visual studio project files for those modules? and make them built automatically?
<br><br>Regards,<br>- Ralf<br><br></div></div>