Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Depreciation of pip --no-binary #53

Closed
JeffreyBlinksma opened this issue Dec 5, 2022 · 2 comments
Closed

Depreciation of pip --no-binary #53

JeffreyBlinksma opened this issue Dec 5, 2022 · 2 comments
Assignees

Comments

@JeffreyBlinksma
Copy link
Collaborator

DEPRECATION: --no-binary currently disables reading from the cache of locally built wheels. In the future --no-binary will not influence the wheel cache. pip 23.1 will enforce this behaviour change. A possible replacement is to use the --no-cache-dir option. You can use the flag --use-feature=no-binary-enable-wheel-cache to test the upcoming behaviour. Discussion can be found at https://github.com/pypa/pip/issues/11453
@ThatOneNovaGuy
Copy link
Collaborator

--no-binary tag on line 7 has been removed and replaced with suggested --no-cache-dir, working on rewriting Dockerfile in pip-dep-test branch to resolve remaining errors.

@JeffreyBlinksma
Copy link
Collaborator Author

JeffreyBlinksma commented Dec 22, 2022

According to pypa/pip issue #11453 our specific usecase will still be supported.

We want --no-binary to mean only one thing, namely "don't download wheels".
Since this is the reason we use --no-binary, this does not need to be changed in the code.

AKA: guess which two dumb fucks didn't read the docs? us. it was us.
-Nova

@JeffreyBlinksma JeffreyBlinksma closed this as not planned Won't fix, can't repro, duplicate, stale Dec 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants