Quentin Peter

That is not an helpful error :/ is this only an issue when you cross python versions correct? @ccordoba12 what versions os python did you use?

> Sorry, that's what I'm seeing but I can get more info if you need it. I assume `_class_setstate ` indeed exists (https://github.com/cloudpipe/cloudpickle/blob/f111f7ab6d302e9b1e2a568d0e4c574895db6a6e/cloudpickle/cloudpickle.py#L1150) and that the `AttributeError` was raised in...

> Cloudpickle can only be used to send objects between the exact same version of Python. That is not ideal. I guess the problem is that if named tuple is...

Most comms send and receive basic objects (strings, list, dict, float) but some are more general and this will be a problem. (get/set_value for example)

@ccordoba12 with a few adjustments we can replace cloudpickle with json so this class of problem disappears

The problem here is that cloudpickle only works for the exact same version of python, and we use in general different versions of python, and therefore can not use cloudpickle....

What we could do is to use cloudpickle only in get/set_value?

I guess most users are using the same interpreter for the kernel and frontend, so the issue with cloudpickle doesn’t show up that much. If the only use for cloudpickle...

> If the only use for cloudpickle is the variable explorer, then it should be used only there. This will greatly simplify the handling of errors. We could for example...

> I don't understand this. How can we unpickle an object if its class is not installed on the Spyder side? from cloud pickle doc: `Among other things, cloudpickle supports...