20:42 <mjacob> mattip: i think the bug about cpickle was mostly "python's i/o api design is complete garbage, here see that even cpickle uses it wrong"

20:50 <mjacob> mattip: but maybe i can still help?

21:05 <krono> 😂

21:38 <mjacob> mattip: found the culprit: https://github.com/cloudpipe/cloudpickle/blob/6a0e12d058d1bd3ab26ec000ac2249b4ee7e9c9f/cloudpickle/cloudpickle_fast.py#L654

21:38 <mjacob> the comment even states that it won't work with the pure python pickler

21:57 <mjacob> mattip: unfortunately, i won't have time to write a comment in the bug tracker tonight and i'll travel starting from tomorrow (not sure if i manage to do it in the train)

22:01 <mjacob> mattip: so the pure python pickler class has a dispatch attribute that's used internally, so setting it messes things up

22:02 <mjacob> mattip: i would suggest 1) to remove the dispatch "compatibility" attribute completely, as it can never work with pure python picklers 2) (although probably not needed to fix these test failures) to decouple pypy-specific code from pure-pickle-specific code