Documentation URL doesn't follow the patter
See original GitHub issue📚 Documentation
You can get the torchtext
documentation here: https://pytorch.org/text
torchaudio
also has a similar URL: https://pytorch.org/audio
However, vision has a completely different URL: https://pytorch.org/docs/stable/torchvision
I think it is better to standardize the addresses, and make a common pattern https://pytorch.org/{package} for any torch{package}
Issue Analytics
- State:
- Created 3 years ago
- Comments:17 (13 by maintainers)
Top Results From Across the Web
URL Pattern API - MDN Web Docs
The URL Pattern API defines a syntax that is used to create URL pattern matchers. These patterns can be matched against URLs or...
Read more >Use Default URL Pattern - Contentstack
Note: The Default URL Pattern feature is only available for the “Webpage” content types that are of “Multiple” type. It is not available...
Read more >URL dispatcher - Django documentation
If no URL pattern matches, or if an exception is raised during any point in this process, Django invokes an appropriate error-handling view....
Read more >URLs: Some Practical Advice | MLA Style Center
The MLA Handbook advises writers to truncate a URL in one specific way (by omitting the protocol and //). If you need to...
Read more >url-pattern | Junos OS | Juniper Networks
Use URL pattern lists to create custom URL category lists. These are lists of patterns that bypass scanning. Warning: Custom category does not...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
https://pytorch.org/vision is working now. Thanks all for your help on this.
I’ll close the issue.
it’s historical.
I’m okay with harmonizing them in pytorch.org/vision , pytorch.org/text , pytorch.org/audio and providing a link to them in pytorch.org/docs However, I worry that the people who use the search bar in pytorch.org/docs will start missing the results from before, so thinking that through is important