-
Notifications
You must be signed in to change notification settings - Fork 684
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
Add devices/properties badges #2321
Conversation
fb5a293
to
55d2c61
Compare
@@ -0,0 +1,97 @@ | |||
Supported Features |
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.
thoughts on renaming this "Supported Properties" or something of that nature? could be slightly confusing to use feature as both the overall feature set and as a subset (autograd/torchscript)
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.
Yes! I was also feeling that "feature" is overloaded here. Thanks for the suggestion. Will do.
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.
Updated. It still uses the ambiguous feature
term. Let me know what you think.
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.
maybe "Supported PyTorch Features" to reflect that they're native to pytorch?
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.
I am thinking to mention numerical compatibility with other libraries such as librosa and Kaldi, so let me follow-up on this one.
Co-authored-by: Caroline Chen <carolinechen@fb.com>
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.
just cosmetic things — looks good overall
@@ -0,0 +1,97 @@ | |||
Supported Features |
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.
maybe "Supported PyTorch Features" to reflect that they're native to pytorch?
Co-authored-by: hwangjeff <hwangjeff@users.noreply.github.com>
@mthrok has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Hey @mthrok. |
Summary: Add badges of supported properties and devices to functionals and transforms. This commit adds `.. devices::` and `.. properties::` directives to sphinx. APIs with these directives will have badges (based off of shields.io) which link to the page with description of these features. Continuation of pytorch#2316 Excluded dtypes for further improvement, and actually added badges to most of functional/transforms. Pull Request resolved: pytorch#2321 Reviewed By: hwangjeff Differential Revision: D35489063 Pulled By: mthrok fbshipit-source-id: f68a70ebb22df29d5e9bd171273bd19007a81762
Add badges of supported properties and devices to functionals and transforms.
This commit adds
.. devices::
and.. properties::
directives to sphinx.APIs with these directives will have badges (based off of shields.io) which link to the
page with description of these features.
Continuation of #2316
Excluded dtypes for further improvement, and actually added badges to most of functional/transforms.