You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@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.
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.txtAlternative Solutions
cant, i dont know how to use heroku
Additional context
nope
Code of Conduct
The text was updated successfully, but these errors were encountered: