-
-
Notifications
You must be signed in to change notification settings - Fork 181
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
dump_session
fails with from numpy import *
#79
Comments
I'd suggest pickling everything via |
(@nikohansen) note that this works:
and this woks:
however, |
Just to emphasize my users perspective: my main concern is not that |
With trace turned on, we see some odd behavior:
|
This is a fun one. Numpy's scalar type system generates a bunch of types automatically, distinguishing for example between ULONG and ULONGLONG - which are the same on 64-bit systems, and end up with the same name but different type objects:
These then also get dragged into all of the Numpy type conversion apparatus, like |
This is still happening for me with dill 0.2.8.2
And even though a foo.pkl gets created, I can't load it from a new session
|
@binaryfunt: Try it with
Then in a new session:
|
I'm having the same problem on this thread; I use 'from numpy import *' because I love Travis Oliphant's original work, read his original documentation, and followed his recommendation to use NumPy in this way. (Rest of comment deleted) |
@shepware: if you are getting an error, what you've reported is not sufficient information:
I don't see this error in any of the environments and versions that I test on, so I'd need information on OS and versions of Feel free to open this in a new ticket, and if it's a duplicate, I'll manage that. Secondly... I worked in finance, and to help facilitate storing complex objects on disk on in a database, I created |
Thanks I’ll check that out. Deleting my original questions so as not to completely throw IEX under the bus for mission abandonment on democratizing Wall Street, or fill up this thread with non-replicable errors. |
Importing numpy in this common way leads to pickle failures.
Specifically:
and very very probably several others.
This is a bit of a big request to add all of the
numpy
top-level objects, but it's a very common case.The text was updated successfully, but these errors were encountered: