-
Notifications
You must be signed in to change notification settings - Fork 27.7k
PyTorch serialization formats #31877
Copy link
Copy link
Closed
Labels
high priorityoncall: jitAdd this issue/PR to JIT oncall triage queueAdd this issue/PR to JIT oncall triage queuetriage reviewtriagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate moduleThis issue has been looked at a team member, and triaged and prioritized into an appropriate module
Metadata
Metadata
Assignees
Labels
high priorityoncall: jitAdd this issue/PR to JIT oncall triage queueAdd this issue/PR to JIT oncall triage queuetriage reviewtriagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate moduleThis issue has been looked at a team member, and triaged and prioritized into an appropriate module
@soumith, @ezyang, as PyTorch serialization formats keep changing and evolving, is there a scheme to name and version the different formats to avoid confusion?
Something along these lines:
sys_info,pickle,storages,tensors8a0a6cfc9c...signatureconstants.pklandmodel.jsonconstants.pklanddata.pkldata.pklbut no codecc @ezyang @gchanan @zou3519 @suo