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

Is there a way to use --no-deps in requirements.txt #12474

Closed
1 task done
TheKidThatCodes opened this issue Jan 13, 2024 · 3 comments
Closed
1 task done

Is there a way to use --no-deps in requirements.txt #12474

TheKidThatCodes opened this issue Jan 13, 2024 · 3 comments
Labels
S: needs triage Issues/PRs that need to be triaged type: feature request Request for a new feature

Comments

@TheKidThatCodes
Copy link

What's the problem this feature will solve?

i need to install a package with no dependencies so i can manually chose the versions of the package's dependencies

Describe the solution you'd like

--no-deps flag in requirements.txt

Alternative Solutions

cant, i dont know how to use heroku

Additional context

nope

Code of Conduct

@TheKidThatCodes TheKidThatCodes added S: needs triage Issues/PRs that need to be triaged type: feature request Request for a new feature labels Jan 13, 2024
@kailando
Copy link

What's the problem this feature will solve?

i need to install a package with no dependencies so i can manually chose the versions of the package's dependencies

Describe the solution you'd like

--no-deps flag in requirements.txt

Alternative Solutions

cant, i dont know how to use heroku

Additional context

nope

Code of Conduct

Impossible. Voting to close

@gwerbin
Copy link

gwerbin commented Jan 22, 2024

@kailando we just ran into this problem in AWS MWAA as well. We use pip-compile to create a "locked" requirements.txt, then fetch all wheels with pip download, which we upload to an S3 bucket. This is actually recommended practice by AWS, and it works well most of the time.

However we just recently hit an issue where somehow Pip got confused and was trying to install a dependency that it should not have been trying to download. Normally the recommended advice in this situation is to run pip install --no-deps, because we are already installing the full dependency tree from a hard-locked requirements.txt and pre-downloaded wheels.

It would be convenient if we could pass this option in through a requirements file, to make it easy to control how Pip works in cloud platforms. Otherwise each platform would have to expose this option in some ad-hoc setting, which IMO is worse than just being able to do it in Pip.

If it's technically impossible of course that's understandable, and likewise if it's flatly something that Pip does not want to support. But I did at least want to highlight that this would have a legitimate use case.

@uranusjr
Copy link
Member

Duplicate of #10837

@uranusjr uranusjr marked this as a duplicate of #10837 Jan 23, 2024
@uranusjr uranusjr closed this as not planned Won't fix, can't repro, duplicate, stale Jan 23, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 23, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
S: needs triage Issues/PRs that need to be triaged type: feature request Request for a new feature
Projects
None yet
Development

No branches or pull requests

4 participants