Zanie Blue
Zanie Blue
This seems reasonable, I wonder if it should be opt-in though?
We have this as `--show-version-specifiers` in `uv pip tree`
That's fine with me too.
Hi! Thanks for contributing this fix. I applied a small patch (https://github.com/astral-sh/uv/pull/6740/commits/4d4cd93ada926005bfeec5eb39c50919b209b734) to move the filtering up where we do all the other filtering. What do you think?
Tested with ``` ❯ PATH="/Users/zb/Library/Application Support/uv/python/cpython-3.10.13-macos-aarch64-none/bin/:$PATH" uv python list | wc -l 16 ❯ PATH="/Users/zb/Library/Application Support/uv/python/cpython-3.10.13-macos-aarch64-none/bin/:$PATH" ./target/debug/uv python list | wc -l 15 ```
Oh.. hm. I'll need to look closer.
Reading about this in https://unix.stackexchange.com/questions/176235/fork-and-how-signals-are-delivered-to-processes Seems like both the child and parent should receive the signal already? That's why above we say: > // Ignore signals in the parent process,...
More interesting discussion in https://github.com/docker/compose/issues/10898#issuecomment-1680334699 and https://github.com/docker/cli/issues/4402#issuecomment-1681236915 > I think that when the CLI receives a signal which is customarily used to ask processes to gracefully terminate, the CLI should...
Basically — I think we should be forwarding all signals to the child process but we'll need an exception for SIGINT in an interactive session because it's probably _already_ been...
That's also discussed briefly in #3095