Message 294546 - 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	Marandil
Recipients	Jorge Herskovic, Marandil, davin, ned.deily, sbt
Date	2017-05-26.11:09:31
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1495796971.74.0.470320038403.issue24484@psf.upfronthosting.co.za>
In-reply-to

Content
I can confirm, I have managed to accidentally reproduce this issue on a custom build of 3.6.0 on RHEL. sys.version: '3.6.0 (default, Jan 18 2017, 11:23:11) [GCC 4.4.7 20120313 (Red Hat 4.4.7-16)]' The issue popped out of nowhere, on a code that was working w/out any hiccups on multiple systems; after an insignificant change was made to an unrelated part of code. I managed to "patch it up" by forcingly closing and joining all Queues before letting the main process to stop. Unfortunately, I cannot share the repro code (it's a) too large, b) closed), but I can confirm the issue was still open in 3.6.0.

I can confirm, I have managed to accidentally reproduce this issue on a custom build of 3.6.0 on RHEL.
sys.version:
'3.6.0 (default, Jan 18 2017, 11:23:11)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-16)]'

The issue popped out of nowhere, on a code that was working w/out any hiccups on multiple systems; after an insignificant change was made to an unrelated part of code.

I managed to "patch it up" by forcingly closing and joining all Queues before letting the main process to stop.

Unfortunately, I cannot share the repro code (it's a) too large, b) closed), but I can confirm the issue was still open in 3.6.0.

History
Date	User	Action	Args
2017-05-26 11:09:31	Marandil	set	recipients: + Marandil, ned.deily, sbt, davin, Jorge Herskovic
2017-05-26 11:09:31	Marandil	set	messageid: <1495796971.74.0.470320038403.issue24484@psf.upfronthosting.co.za>
2017-05-26 11:09:31	Marandil	link	issue24484 messages
2017-05-26 11:09:31	Marandil	create