I looked into CloudPickle a while back, and would be supportive of the change.
On Mon, Jul 1, 2019 at 11:06 PM Valentyn Tymofieiev wrote:
>
> I have checked that cloudpickle (an alternative to dill) is able to pickle
> and unpickle typing types on Python 3.5, 3.6, which seems to be a recent
> c
I have checked that cloudpickle (an alternative to dill) is able to pickle
and unpickle typing types on Python 3.5, 3.6, which seems to be a recent
change, see:
https://github.com/cloudpipe/cloudpickle/issues/63#issuecomment-501624383.
I am evaluating cloudpickle as a potential avenue to address s
(2) seems reasonable.
On Tue, May 14, 2019 at 3:15 AM Udi Meiri wrote:
>
> It seems like pickling of typing types is broken in 3.5 and 3.6, fixed in 3.7:
> https://github.com/python/typing/issues/511
>
> Here are my attempts:
> https://gist.github.com/udim/ec213305ca865390c391001e8778e91d
>
>
> M
It seems like pickling of typing types is broken in 3.5 and 3.6, fixed in
3.7:
https://github.com/python/typing/issues/511
Here are my attempts:
https://gist.github.com/udim/ec213305ca865390c391001e8778e91d
My ideas:
1. I know that we override type object handling in pickler.py
(_nested_type_wra
