Skip to content

Add --no-binary and --only-binary support to requirements.txt#2680

Merged
charliermarsh merged 1 commit intomainfrom
charlie/no-binary
Mar 27, 2024
Merged

Add --no-binary and --only-binary support to requirements.txt#2680
charliermarsh merged 1 commit intomainfrom
charlie/no-binary

Conversation

@charliermarsh
Copy link
Copy Markdown
Member

Summary

Closes #1461.

@charliermarsh charliermarsh added enhancement New feature or improvement to existing functionality compatibility Compatibility with a specification or another tool labels Mar 27, 2024
@charliermarsh charliermarsh marked this pull request as ready for review March 27, 2024 00:05
@charliermarsh charliermarsh enabled auto-merge (squash) March 27, 2024 00:15
@Jacobus-afk
Copy link
Copy Markdown

Hi @charliermarsh , apologies if this isn't the right place to ask this. Should using uv version 0.4.25 mean that it would be able to handle --no-binary in a requirements.txt file?

my requirements file:

astroid==2.0.4
Django==2.2
python-dotenv
djangorestframework==3.11.0
isort==4.3.4
lazy-object-proxy==1.3.1
mccabe==0.6.1
psycopg2==2.9.6 --no-binary psycopg2
pycodestyle==2.4.0
pytz==2018.5
six==1.11.0
whitenoise==5.1.0
wrapt==1.10.11

running uv pip sync requirements.txt gives me the following error

error: Expected `--hash`, found `"--no-binary"` at requirements.txt:8:17

@zanieb
Copy link
Copy Markdown
Member

zanieb commented Oct 27, 2024

@Jacobus-afk I believe it has to be on its own line

@Jacobus-afk
Copy link
Copy Markdown

Thanks for the response @zanieb, that does fix it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

compatibility Compatibility with a specification or another tool enhancement New feature or improvement to existing functionality

Projects

None yet

Development

Successfully merging this pull request may close these issues.

uv pip compile|install can't handle --no-binary lxml option in requirements file

3 participants