Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: mention that python requirements need to be specified using full address from the root #21293

Merged
merged 2 commits into from
Aug 13, 2024
Merged

docs: mention that python requirements need to be specified using full address from the root #21293

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d2c0d36
docs: mention that python requirements need to be specified using ful…
AlexTereshenkov Aug 12, 2024
14dbdb3
lint
AlexTereshenkov Aug 13, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion src/python/pants/backend/python/subsystems/python_tool_base.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,7 +124,9 @@ def _install_from_resolve_help(cls) -> str:

Values can be pip-style requirements (e.g., `tool` or `tool==1.2.3` or `tool>=1.2.3`),
or addresses of `python_requirement` targets (or targets that generate or depend on
`python_requirement` targets).
`python_requirement` targets). Make sure to use the `//` prefix to refer to targets
using their full address from the root (e.g. `//3rdparty/python:tool`). This is necessary
to distinguish address specs from local or VCS requirements.

The lockfile will be validated against the requirements - if a lockfile doesn't
provide the requirement (at a suitable version, if the requirement specifies version
Expand Down
Loading