Author aeros
Recipients aeros, asvetlov, chris.jerdonek, njs, vstinner, yselivanov
Date 2020-05-09.21:14:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1589058856.62.0.490378602784.issue38323@roundup.psfhosted.org>
In-reply-to
Content
> Would it make sense to deprecate it and stick with ThreadedChildWatcher?

I had proposed deprecating it in another bpo issue, but it was brought up that MutliLoopWatcher had only been added recently in 3.8. So, it might be a bit too soon to deprecate it already.

Although I suppose that if there are several complex and difficult to resolve issues with the implementation, it may very well be less damaging to deprecate it now rather than after it's gained a decent a decent amount of usage.
History
Date User Action Args
2020-05-09 21:14:16aerossetrecipients: + aeros, vstinner, njs, asvetlov, chris.jerdonek, yselivanov
2020-05-09 21:14:16aerossetmessageid: <1589058856.62.0.490378602784.issue38323@roundup.psfhosted.org>
2020-05-09 21:14:16aeroslinkissue38323 messages
2020-05-09 21:14:16aeroscreate