janhoy commented on PR #50:
URL: https://github.com/apache/solr-orbit/pull/50#issuecomment-5095266363

   In last commit I had Claude bring docs up to date with uv (remove pip / 
pyenv mentions):
   
   Three docs still described the old pyenv/pip workflow.
   
   **`PYTHON_SUPPORT_GUIDE.md`** — the "add a Python version" checklist:
   - Removed the `.ci/variables.json` step and the dead `pyinst`/`check-pip` 
Makefile snippet (those targets no longer exist)
   - Now points at the actual post-uv sources of truth: `pyproject.toml` 
(`requires-python`, classifiers, tox `envlist` — with a note that tox-uv 
auto-downloads missing interpreters), `.python-version`, and the `it<VERSION>` 
Makefile targets
   - Testing steps: `pyenv local <version>` → `uv sync --extra develop --python 
<version>`
   - Binary-path example: `~/.pyenv/shims/solr-orbit` → `.venv/bin/solr-orbit`
   
   **`docs/user-guide/install-and-configure/installing.md`**:
   - Prerequisites: replaced the Python + pip bullets with a single **uv** 
bullet (uv downloads Python 3.12 automatically)
   - Replaced the pyenv tip with a "uv manages Python versions" tip incl. 
install one-liners
   - Install / virtualenv / developer / upgrade flows: `pip install -e .` + 
manual `python3 -m venv` → `uv sync` / `uv sync --extra develop`; the separate 
"Virtual environment (recommended)" section was folded away since `uv sync` 
always creates `.venv`
   
   **`docs/quickstart.md`**: `pip install -e .` → `uv sync` + `source 
.venv/bin/activate`
   
   **Verified:** ran the documented quickstart flow from scratch — plain `uv 
sync` then `.venv/bin/solr-orbit --version` → `solr-orbit 0.1.0` ✅. A final 
grep confirms no stale pyenv/pip instructions remain under `docs/` or the 
guides.
   
   **Note:** `.ci/variables.json` was now completely orphaned so I removed it


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to