conda env instructions

[anuragprat1k]

Description

Fixes # (issue)

Type of change

Please check the options that are relevant.

• Bug fix (non-breaking change that fixes an issue)
• Proposes a change (non-breaking change that isn't necessarily a bug)
• Refactor
• New feature (non-breaking change that adds a new functionality)
• Breaking change (fix or feature that would break some existing functionality downstream)
• This is a unit test
• Documentation only change

Type of requested review

• I want a thorough review of the implementation.
• I want a high level review.
• I want a deep design review.

Checklist:

• I have performed manual end-to-end testing of the feature in my environment.
• I have added Docstrings and comments to the code.
• I have made changes to existing documentation where needed.
• I have added tests that show that the PR is functional.
• New and existing unit tests pass locally with my changes.
• I have added relevant collaborators to review the PR before merge.

[soumith]

if we are going the route of mandating conda, which I really dont mind, then we should also move the installation of PyTorch into the conda install so that it isn't brittle around the version of CUDA installed.

Approving this for now, will move some of the requirements.txt stuff into conda commands myself.

In the "Dependencies", now you have to specify Anaconda / Miniconda

[anuragprat1k]

if we are going the route of mandating conda, which I really dont mind, then we should also move the installation of PyTorch into the conda install so that it isn't brittle around the version of CUDA installed.

Approving this for now, will move some of the requirements.txt stuff into conda commands myself.

In the "Dependencies", now you have to specify Anaconda / Miniconda

Currently, the dependencies say "(Anaconda recommended)". Going to leave it at that. Agree with your idea of moving stuff from requirements.txt for stronger consistency.