Support no-op --no-compile

[henryiii]

It would be nice to simply ignore --no-compile, rather than throw an error, to make it easier to swap pip and uv.

[charliermarsh]

Thanks, I assumed we did this already. Will add.

[sam-goodwin]

I think I ran into this with uv pip compile. Just wanted a way to create a requirements.txt from pyproject.toml but it built pyspark which took 1-2 minutes. Expected the operation to be instant.

[zanieb]

@sam-goodwin this is totally separate — --no-compile means do not compile .pyc files. You're looking for --only-binary.

[henryiii]

That's not what --no-compile means. It means skip making .pyc files from .py files, which uv already does, and is opt-in for pip.

[sam-goodwin]

Thanks @zanieb and @henryiii , sorry for the confusion.

[staaam]

@charliermarsh I'd like to reopen this issue, since --no-compile flag is still not support. Getting this error:

$ uv pip install --no-compile test
error: unexpected argument '--no-compile' found

  tip: a similar argument exists: '--no_compile'

which kind of misses the point (tested on uv==0.2.13)

[charliermarsh]

It's --no-compile-bytecode, but we can add an alias.

[charliermarsh]

Fixed in #4453.