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 josh.r
Recipients Victor de la Fuente, davin, josh.r
Date 2017-01-19.04:19:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1484799545.49.0.0576972559449.issue29293@psf.upfronthosting.co.za>
In-reply-to
Content
Looks like, despite what the multiprocessing.Condition docs say (claiming it's an alias for threading.Condition), at least in Python 3.5, it's a completely separate animal from multiprocessing.synchronize, and the notify method on it doesn't take any parameters.

Seems like an obvious thing to fix; the parameter is defaulted anyway, so existing code should continue to work, and it makes multiprocessing swap in for threading more seamlessly.
History
Date User Action Args
2017-01-19 04:19:05josh.rsetrecipients: + josh.r, davin, Victor de la Fuente
2017-01-19 04:19:05josh.rsetmessageid: <1484799545.49.0.0576972559449.issue29293@psf.upfronthosting.co.za>
2017-01-19 04:19:05josh.rlinkissue29293 messages
2017-01-19 04:19:04josh.rcreate