Jurko Gospodnetić added the comment:

I can reproduce this most easily if I run a command like:

  clean.cmd & run.py

where clean.cmd is any short batch script and run.py is a file containing only 
the '#! python3' shabang line.

The batch script in front is not necessary, and I've originally been 
reproducing the issue without it, but the problem seems much easier to 
reproduce with it, most likely because is slightly delays the Python startup 
and thus makes it easier for the Ctrl-C signal to kick in early enough during 
Python startup.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue19983>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to