-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Cannot unpickle data frame made with 0.19.2 after upgrade to 0.20.1 #16474
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Going from panda 0.18.1 to 0.20.1 I encountered the same problem when loading with joblib. When you fix this (see the first workaround), there is an error After workaround 2, files load. It seems that in my case this is more of a question for joblib devs. Two (ugly) workarounds:
|
see the above and simply use pd.read_pickle |
I would if I could. But... I have a complex class (consisting of numpy objects, pandas series and dataframes, dictionaries ...), stored in a compressed joblib archive, so pd.read_pickle is of no use to me. As I said, this might be useful for joblib developers as for now it is impossible to load any joblib archive created when pandas < 0.20. I first had to downgrade pandas and now I'm using the above workarounds. |
@matjazk Would you like to open an issue at joblib for this? |
Already did and passed @jreback's suggestion. |
@mhooreman the timings of "reading old" look suspiciously consistent with "writing". Are you sure you timed the correct thing? |
I need to double check, but I'm sure about the performance difference while
reading: I got performance issues and I converted to fix those.
Le 8 juin 2017 5:50 PM, "Joris Van den Bossche" <[email protected]>
a écrit :
… @mhooreman <https://github.com/mhooreman> the timings of "reading old"
look suspiciously consistent with "writing". Are you sure you timed the
correct thing?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16474 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHCDlsDJNzuoFr8GMwsOIyQwCFGjUEZKks5sCBhTgaJpZM4Nku1h>
.
|
@mhooreman of course its slower. its falling back to the python based unpickler which is much more flexible. so you can either have fast or correctness. you get to choose. |
I got the same problem when unpickling the data in pandas 0.20.2. I have used
|
@TheodoreZhao If you have this error with |
its an open issue: #5924 if you want to submit a PR to do this, its not difficult. |
Hello,
Problem description
When we create a data frame with pandas ≤ 0.19.2 and pickle it (using pickle.dump), it is not possible to unpickle it using pandas 0.20.1.
First analysis
pandas.indexes
has been refactored topandas.core.indexes
.Proposal
It would be great to have:
Thanks a lot for your help,
Best regards.
The text was updated successfully, but these errors were encountered: