Message 396542 - 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	moi90
Recipients	davin, iritkatriel, moi90, pitrou
Date	2021-06-26.06:59:56
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1624690796.64.0.349673904917.issue41539@roundup.psfhosted.org>
In-reply-to

Content
Yes, I think it should at least be documented. But then it practically says: "Do not use print in your library because it might be used in a threading context" This sounds unacceptable to me. It would be great to "just make it work". > I debugged it a bit and I think the race may be between your print statement and the util._flush_std_streams() Why would print deadlock with a flush?

Yes, I think it should at least be documented.

But then it practically says: "Do not use print in your library because it might be used in a threading context" This sounds unacceptable to me. 

It would be great to "just make it work".

> I debugged it a bit and I think the race may be between your print statement and the util._flush_std_streams()

Why would print deadlock with a flush?

History
Date	User	Action	Args
2021-06-26 06:59:56	moi90	set	recipients: + moi90, pitrou, davin, iritkatriel
2021-06-26 06:59:56	moi90	set	messageid: <1624690796.64.0.349673904917.issue41539@roundup.psfhosted.org>
2021-06-26 06:59:56	moi90	link	issue41539 messages
2021-06-26 06:59:56	moi90	create