-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Recommend cpython agnosticism in cpp custom op tutorial #3250
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/tutorials/3250
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 7b1ab2c with merge base 15ef015 (): This comment was automatically generated by Dr. CI and updates every 15 minutes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor editorial nits.
advanced_source/cpp_custom_ops.rst
Outdated
This ``setup`` would build one wheel that could be installed across multiple CPython | ||
versions ``>=3.9``. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Uh, does the wheel have the right platform tags to reject Python 3.8? Or is the advice to people to always use the smallest version that is not deprecated?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the latter hehe
i haven't checked against 3.8, but it was cuz i chose 3.9 as the min version out there. will include a sentence for that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah we need to tell people that the numbers they choose should be the min version pytorch supports
9e388d2
to
1372553
Compare
Description
In 2.6, PyTorch will better support python agnosticism in custom operators. This PR updates the tutorial to recommend the torch.ops.load_library path so that future custom op writers can follow this better pattern instead. These changes are paired with updates to our example extension-cpp repo that have now landed: pytorch/extension-cpp#105
Checklist