"Fredrik Lundh" <fredrik@pythonware.com> writes:
Thomas Heller wrote:
I suggest to remove the imports of the pywin32 stuff, it's not needed and confuses tools like freeze or py2exe.
That's really a problem with the tools, not with the module.
Yep.
Demanding that users of a dynamic language use only static linking is really silly.
Wouldn't it be better to invent a (pragma-level) syntax so that a module can inform the tool about its intentions?
Yes. But I don't think I have the energy to discuss that here, and don't feel it would be easy to get this into the core.
(removing the pywin stuff from the module would hamper development of new features, and also make it harder to verify that the _subprocess module works as it should).
Hm, that what the tests are for, and not code that is never executed. A working solution would be to comment out this stuff, or put it into an 'if 0:' block, in both cases one could easily activate it again for experimentation. Thomas