pytorch / pytorch/pytorch.github.io
Suggestion: Prioritize Pip Package Manager in Installation Guide Reflecting Anaconda Channel Deprecation
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 285
- Forks
- 317
- PR merge metrics
- No merged PRs in 30d
Description
🕋 Website
I would like to suggest an improvement to the PyTorch installation page to better reflect the current packaging and distribution recommendations.
To Reproduce
- Go to the PyTorch website: https://pytorch.org
- Navigate to the 'Get Started' or 'Installation' section
- Observe the current order of packaging options listed
Expected behavior
The "Pip" package manager should be listed first under the "Package" section of the installation guide, as it is now the primary recommended method for installing PyTorch, especially after the deprecation of the official Anaconda channel.
Screenshots
Desktop:
- OS: Ubuntu22.04
Additional context
Given the recent deprecation of PyTorch's official Anaconda channel (Issue https://github.com/pytorch/pytorch/issues/138506), it would be beneficial for users if the installation guide on the website reflects this change by prioritizing Pip. This would provide a more streamlined and clear installation process for new users and align with the current maintenance and user download trends.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the PyTorch website's Get Started or Installation page and inspect the Package section's current ordering. Confirm the guidance about the deprecated official Anaconda channel, then update the ordering so Pip is listed first. Done means the installation guide clearly presents Pip as the primary package option.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100