"Fredrik Lundh"
Thomas Heller wrote:
(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.
if you remove the _subprocess driver, it is executed. _subprocess is just a win32all emulator...
To be honest, I'm against code in the core that depends on whether pywin32 is installed or not.
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.
does py2exe support "if 0" blocks?
py2exe uses modulefinder to scan the byte code of compiled modules, and Python doesn't generate code for 'if 0' blocks, so, yes. Thomas