Message 188026 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	r.david.murray
Recipients	pitrou, r.david.murray, terry.reedy
Date	2013-04-28.21:32:34
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1367184754.83.0.680961929564.issue17863@psf.upfronthosting.co.za>
In-reply-to

Content
Indeed, in both 3.3.0 non-debug and 3.4 tip debug, python starts consuming 100% of the CPU. I'm guessing there is some subtlety involving the new IO system involved here. Python 2.7 debug build acts as you indicate for your 2.7 non-debug build. All my tests are on linux, and I had to kill -HUP the python process. As you say, ctl-C (and ctl-D, not surprisingly) were ignored.

Indeed, in both 3.3.0 non-debug and 3.4 tip debug, python starts consuming 100% of the CPU.  I'm guessing there is some subtlety involving the new IO system involved here.

Python 2.7 debug build acts as you indicate for your 2.7 non-debug build.

All my tests are on linux, and I had to kill -HUP the python process.  As you say, ctl-C (and ctl-D, not surprisingly) were ignored.

History
Date	User	Action	Args
2013-04-28 21:32:34	r.david.murray	set	recipients: + r.david.murray, terry.reedy, pitrou
2013-04-28 21:32:34	r.david.murray	set	messageid: <1367184754.83.0.680961929564.issue17863@psf.upfronthosting.co.za>
2013-04-28 21:32:34	r.david.murray	link	issue17863 messages
2013-04-28 21:32:34	r.david.murray	create