R. David Murray added the comment: 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.
---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29423> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
