docs: mention that python requirements need to be specified using ful…

…l address from the root

src/python/pants/backend/python/subsystems/python_tool_base.py

@@ -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

src/python/pants/backend/python/util_rules/pex.py

@@ -490,6 +490,7 @@ async def get_req_strings(pex_reqs: PexRequirements) -> PexRequirementsInfo:
             else:
                 req_strings.append(req_str_or_addr)
     if specs:
+        1/0
         addrs_from_specs = await Get(
             Addresses,
             UnparsedAddressInputs(

src/python/pants/backend/python/util_rules/pex_requirements.py

@@ -488,7 +488,8 @@ def validate_metadata(
     resolve_config: ResolvePexConfig,
 ) -> None:
     """Given interpreter constraints and requirements to be consumed, validate lockfile metadata."""
-
+    print(consumed_req_strings)
+    print("-------------------------------")
     # TODO(#12314): Improve the exception if invalid strings
     user_requirements = [PipRequirement.parse(i) for i in consumed_req_strings]
     validation = metadata.is_valid_for(