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 r.david.murray
Recipients josh.r, r.david.murray, serhiy.storchaka, spencera, terry.reedy
Date 2017-02-03.13:41:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1486129299.99.0.163268933104.issue29423@psf.upfronthosting.co.za>
In-reply-to
Content
See the issue I linked to.  RLocks were incorrectly pickled before but the resulting unpickled object was broken.  If the unpickled RLock never got used such code would not break, but the objects were inherently broken and this could lead to hard to debug problem when the objects were used.  Thus we fixed it in 3.6 only so as to not break working code in a maintenance release.  But in 3.6 and later, RLocks (among other things that were also broken) are no longer pickleable.
History
Date User Action Args
2017-02-03 13:41:40r.david.murraysetrecipients: + r.david.murray, terry.reedy, serhiy.storchaka, josh.r, spencera
2017-02-03 13:41:39r.david.murraysetmessageid: <1486129299.99.0.163268933104.issue29423@psf.upfronthosting.co.za>
2017-02-03 13:41:39r.david.murraylinkissue29423 messages
2017-02-03 13:41:39r.david.murraycreate