[Twisted-Python] Re: Problems with signalProcess on Windows

Brian Granger ellisonbg.net at gmail.com
Fri Feb 6 14:07:58 EST 2009

OK, it looks like I solved this.  My external program is a python
program.  I was starting it without the "-u" flag to Python, which
turns on unbuffered output.  Adding the "-u" flag made the error go

I found this tip in the docstrings of the _dumbwin32proc.py Twisted module.

Whoever put that note there, thanks!!!



> [take a deep breath and try to get over how much I dislike Windows]
> So, I am using Twisted's external process capabilities in a
> cross-platform setting.  Almost everything is working now in Windows.
> But, when I try to stop the external program (using
> signalProcess("INT")) that I starting using reactor.spawnProcess, I
> get the following traceback:
>            self.process_transport.signalProcess(sig)
>          File "C:\Python25\lib\site-packages\twisted\internet\_dumbwin32proc.py
> ", line 247, in signalProcess
>            win32process.TerminateProcess(self.hProcess, 1)
>        pywintypes.error: (5, 'TerminateProcess', 'Access is denied.')
> The odd thing is that the process stops just fine.  That is, it tells
> me that it has received SIGINT and is shutting down.
> Any thoughts on why this would happen?  I have no idea where to even
> begin looking.
> Thanks in advanced.
> Cheers,
> Brian

More information about the Twisted-Python mailing list