Skip to content

Conversation

@gchalump
Copy link
Contributor

Summary:
The version compatibility check in _load_library incorrectly uses exact string equality when comparing PyTorch versions, causing false incompatibility warnings.

PyTorch versions typically include build metadata like "2.8.0+cu118" or "2.8.1+cpu", while the compatibility table contains base versions like "2.8".

Differential Revision: D85167315

@netlify
Copy link

netlify bot commented Oct 21, 2025

Deploy Preview for pytorch-fbgemm-docs ready!

Name Link
🔨 Latest commit f7a3613
🔍 Latest deploy log https://app.netlify.com/projects/pytorch-fbgemm-docs/deploys/68f818f788bc340008b5e602
😎 Deploy Preview https://deploy-preview-5041--pytorch-fbgemm-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@meta-codesync
Copy link
Contributor

meta-codesync bot commented Oct 21, 2025

@gchalump has exported this pull request. If you are a Meta employee, you can view the originating Diff in D85167315.

Summary:
X-link: facebookresearch/FBGEMM#2050


The version compatibility check in `_load_library` incorrectly uses exact string equality when comparing PyTorch versions, causing false incompatibility warnings.

PyTorch versions typically include build metadata like `"2.8.0+cu118"` or `"2.8.1+cpu"`, while the compatibility table contains base versions like `"2.8"`.

Differential Revision: D85167315
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant