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 aeros
Recipients aeros, asvetlov, vstinner, yselivanov
Date 2019-10-25.19:54:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Speaking of watchers -- big +1 from me to drop them all at some point. I would start as early as 3.9.

Yeah that was my initial plan, to start the deprecation in 3.9 and finalize the removal in 3.11. We might be able to make an exception for MultiLoopChildWatcher and just remove it from 3.8 though. 

I think it will be necessary to fix the issues in the near future if we want to keep MultiLoopChildWatcher in 3.8 (as they apply to 3.8 and 3.9). I would certainly not be ecstatic about the idea of removing something that was just recently added (similar to how we had to revert the new streaming changes due to API design), but I'm even less in favor of keeping something around that's not stable in a final release. 

Based on my investigation of, it seems like it will be a rather complex issue to solve.
Date User Action Args
2019-10-25 19:54:38aerossetrecipients: + aeros, vstinner, asvetlov, yselivanov
2019-10-25 19:54:38aerossetmessageid: <>
2019-10-25 19:54:38aeroslinkissue38591 messages
2019-10-25 19:54:38aeroscreate