Use uv as the recommended install method in docs #1178
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was wrong?
The install documentation recommended using standard
piponly (python -m pip install libp2p), while the contributing guide and CI/CD useuvas the default tool.This mismatch was confusing for contributors and users trying to mirror the CI environment and follow the recommended workflow.
How was it fixed?
uvas the primary installation method, aligned with the contributing guide and CI.uv-based steps:uvvia the official installer.uv venv venv.uv pip install libp2p.pip-only flow as an “Alternative: using standardpip” section so users withoutuvcan still install the package in the old way.To-Do
Cute Animal Picture
closes #1175