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
[BE] Do not package caffe2 in wheel #87986
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/87986
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit d7ce594: This comment was automatically generated by Dr. CI and updates every 15 minutes. |
If PyTorch is build without caffe2 integration, do not package unusable .py files/headers Followup after pytorch/builder#1181
a41e9be
to
d763e08
Compare
d763e08
to
4e8ae96
Compare
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Merge failedReason: The following mandatory check(s) failed (Rule Dig deeper by viewing the failures on hud Details for Dev Infra teamRaised by workflow job |
Why don't we do wheels, like on other platforms
@pytorchbot merge -f "This is a build only change" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Unless requested otherwise, PyTorch no longer installs most of the header files under the caffe2 directory (see pytorch/pytorch#87986). This breaks our importer code since we need to use the `MakeGuard()` function to execute statements in the event of exceptions. To fix this issue, this patch implements a rudimentary version of PyTorch's ScopeGuard, where once the class variable goes out of scope, it executes a predefined method.
If PyTorch is build without caffe2 integration, do not package unusable .py files/headers Same is true about functorch - don't package it unless building with `functorch` (although, I wonder if we should remove this option at some point in the future) Followup after pytorch/builder#1181 Pull Request resolved: pytorch#87986 Approved by: https://github.com/seemethere
If PyTorch is build without caffe2 integration, do not package unusable .py files/headers Same is true about functorch - don't package it unless building with `functorch` (although, I wonder if we should remove this option at some point in the future) Followup after pytorch/builder#1181 Pull Request resolved: pytorch#87986 Approved by: https://github.com/seemethere
If PyTorch is build without caffe2 integration, do not package unusable .py files/headers Same is true about functorch - don't package it unless building with `functorch` (although, I wonder if we should remove this option at some point in the future) Followup after pytorch/builder#1181 Pull Request resolved: pytorch#87986 Approved by: https://github.com/seemethere
If PyTorch is build without caffe2 integration, do not package unusable .py files/headers Same is true about functorch - don't package it unless building with `functorch` (although, I wonder if we should remove this option at some point in the future) Followup after pytorch/builder#1181 Pull Request resolved: #87986 Approved by: https://github.com/seemethere Co-authored-by: Nikita Shulga <nshulga@meta.com>
If PyTorch is build without caffe2 integration, do not package unusable .py files/headers Same is true about functorch - don't package it unless building with `functorch` (although, I wonder if we should remove this option at some point in the future) Followup after pytorch/builder#1181 Pull Request resolved: pytorch#87986 Approved by: https://github.com/seemethere
If PyTorch is build without caffe2 integration, do not package unusable
.py files/headers
Same is true about functorch - don't package it unless building with
functorch
(although, I wonder if we should remove this option at some point in the future)Followup after pytorch/builder#1181