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 njs
Recipients christian.heimes, ezio.melotti, njs, pitrou, smurfix, vstinner
Date 2018-03-27.21:56:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1522187798.6.0.467229070634.issue32850@psf.upfronthosting.co.za>
In-reply-to
Content
Yes, a PR would be better... also, the two versions of the patch appear to be identical?

CC'ing Antoine and Victor b/c they seem to have written this dangling_threads checking stuff and I'm not sure I understand it :-).

As some extra background: this is in Python's internal testing code, but @smurfix is hitting it because he's working on a third-party asyncio event loop implementation, and re-using test.asyncio to test it. I'm not sure what specifically is causing this to happen, though I guess it has something to do with how trio / trio-asyncio are using threads.

[1] https://github.com/python-trio/trio-asyncio
History
Date User Action Args
2018-03-27 21:56:38njssetrecipients: + njs, pitrou, vstinner, christian.heimes, ezio.melotti, smurfix
2018-03-27 21:56:38njssetmessageid: <1522187798.6.0.467229070634.issue32850@psf.upfronthosting.co.za>
2018-03-27 21:56:38njslinkissue32850 messages
2018-03-27 21:56:38njscreate