Comments not parsed correctly in requirements.txt

[hawko2600]

Summary

I'm using uv to manage ComfyUI. When executing "comfy node restore-dependencies" (this iterates through the comfyui custom_nodes and uses uv pip install to install/update dependencies) I encounter an error indicating that uv is not parsing the requirements.txt correctly.

## ComfyUI-Manager: EXECUTE => ['/var/ai/ComfyUI/comfy/ComfyUI-2026/.venv/bin/python', '-m', 'uv', 'pip', 'install', 'pandas #选装，仅音频AMP归一化用，没有兼容问题']
error: Failed to parse: `pandas #选装，仅音频AMP归一化用，没有兼容问题`
  Caused by: Expected one of `@`, `(`, `<`, `=`, `>`, `~`, `!`, `;`, found `#`
pandas #选装，仅音频AMP归一化用，没有兼容问题
       ^

According to the pip requirements.txt spec, a comment can be at the start of the line or inline with a dependency, as long as the inline comment has a space before the hash. This file complies with the spec, however uv is not expecting the valid comment hash symbol and throws an error.

The module this is failing on is https://github.com/cardenluo/ComfyUI-Apt_Preset/ but the issue persists with other modules too containing comments in the requirements.txt. I've filed an issue against ComfyUI-Apt_Preset to request the requirements.txt have no comments, but I reasonably expect the developer there to go "this is a bug in uv"

Platform

Linux 7.0.6-2-pve x86_64 GNU/Linux

Version

uv 0.11.17 (x86_64-unknown-linux-gnu)

Python version

Using CPython 3.13.5

[koriyoshi2041]

I checked the behavior against both uv and pip.

Inline comments appear to be handled when the requirement is read as a requirements file, e.g. through -r requirements.txt. The reported trace is different: Comfy is passing the whole line, pandas #..., as a single positional package argument to uv pip install.

That matches pip behavior too: pip rejects pandas #comment when it is passed as one CLI requirement string. So this looks less like uv failing to parse a valid requirements.txt, and more like the caller flattening a requirements-file line into a CLI package argument without stripping the inline comment or passing the file via -r.

Likely fixes are on the caller side: pass the requirements file directly with -r, or strip inline comments before invoking one install command per requirement line.