-
Notifications
You must be signed in to change notification settings - Fork 155
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
Compatibility with torch.save()
?
#65
Comments
Hi @dconathan , No it's not possible nor intended. If you care only about security, there's a new If you want stuff like lazy-loading (only part of tensors on files) or the speedups I mention, then you cannot (afaik) use But you can use |
Thanks for the reply! Yeah I looked a little into the src of torch.save and doesn't seem possible... thanks for the links. |
this gist your linked is very cool @Narsil! |
It's exactly what this lib does for CPU, minus handling various torch versions and falling back to slower alternatives. |
Very cool project!
I was wondering if there's possibility to use this package as the "backend" for
torch.save
to enable easier integration with downstream projects that are already usingtorch.save/load
...seems like it might be possible since
torch.save
andtorch.load
have apickle_module=
argument. Something like:The text was updated successfully, but these errors were encountered: