docs: offer pip install nemo-gym as default install path

[lbliii]

Summary

Re-applies the surviving intent of #1311 on top of the docs migration that landed since it was opened.

• README quick start now leads with uv pip install nemo-gym, with git clone … uv sync kept directly below for contributors / unreleased features.
• Installation page gains a Pip tab as the first/default tab.

Why this supersedes #1311

The docs migration independently absorbed ~16 of #1311's 17 files — the README quick-start rewrite, the detailed-setup → installation + new prerequisites split, and the link cleanups are all already on main. #1311's remaining edits would now re-introduce regressions main has since fixed (# H1 bodies, /latest/ link prefixes), so a conflict resolution isn't the right tool. This applies only the one surviving idea — pip install as the default — using main's current conventions (no H1, /get-started/ links).

Blocker resolved

#1311 was blocked on the 0.3.0 PyPI release. That's done:

• nemo-gym 0.3.0 and 0.3.1 are published on PyPI.
• The published wheel ships the quickstart configs and example data (resources_servers/mcqa/configs/mcqa.yaml, .../data/example.jsonl), so the quickstart's repo-relative paths work from a pip install — not just a git clone.

Ref #1191. Supersedes #1311 (recommend closing it).

🤖 Generated with Claude Code

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[github-actions]

🌿 Preview your docs: https://nvidia-preview-lbliii-fix-pr-1311-conflicts.docs.buildwithfern.com/nemo/gym

Here are the markdown pages you've updated:

• nemo/gym/get-started/installation

[kajalj22]

Could you use this python version file instead of the hard coded version? https://github.com/NVIDIA-NeMo/Gym/blob/main/.python-version
Helps keep the flow dynamic for future version bumps

[kajalj22]

Left a minor ask to keep python version dynamic

[lbliii]

Thanks @kajalj22 — good call. Updated the git clone path to use a bare uv venv, which reads the repo's .python-version automatically, so it stays dynamic across future version bumps.

I kept the explicit --python 3.12 on the pip install path only: that flow runs outside a checkout (no .python-version on disk to read), so dropping it would risk landing users on an older default interpreter. Open to other ideas there if you'd prefer a different approach.

[cmunley1]

I do not think pypi should be the default path yet. I don't know many people using it like this, it creates 2 level subdirs for venvs, and its not the best experience for developing locally. I think that it should only become default path as we use it ourselves this way more, or if we develop a environment package registry

[sephmard]

Closing in favor of #1675, which covers the same PyPI install changes to as part of a broader CLI reference update.