uv run --script should imply --no-project

[offbyone]

I'm running into a variation of #8666

I have some uv scripts that are just generic command line tools, not part of a project. If I run them inside a Python project that uses Poetry, though, I get error: No projecttable found in:/Users/offby1/projects/autopub/autopub/pyproject.toml` errors constantly.

I'm using the --script shebang:

#!/usr/bin/env uv --script

I realize that I can add --no-project to it, but really, I think once you're using --script there's a good argument to be made that uv should assume --no-project

[zanieb]

We should just stop throwing that error so aggressively. I don't want --script to imply --no-project in case we want to read things like settings from the project too in the future.

[charliermarsh]

I actually can't reproduce this. Are you still able to? I don't think we discover projects when --script is provided, from reading the code.

[zanieb]

Agreed, could not reproduce.

[offbyone]

I no longer see this either.