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
I have had --find-links=requirements in requirements.txt. It point's to a folder containing proprietary libraries, this folder is deployed alongside the application to CI server, to Heroku, etc.
When I switched to requirements.in and pip-tools, my compiled requirements.txt does not contain it anymore. I know I can supply find-links switch in other ways in target environment, but leaving it in the requirements.txt file is the most simple and robust solution — no need to configure each and every environment separately.
It would be good to somehow whitelist or otherwise put --find-links=requirements in compiled `requirements.txt.
The text was updated successfully, but these errors were encountered:
I have had
--find-links=requirements
inrequirements.txt
. It point's to a folder containing proprietary libraries, this folder is deployed alongside the application to CI server, to Heroku, etc.When I switched to
requirements.in
andpip-tools
, my compiledrequirements.txt
does not contain it anymore. I know I can supplyfind-links
switch in other ways in target environment, but leaving it in therequirements.txt
file is the most simple and robust solution — no need to configure each and every environment separately.It would be good to somehow whitelist or otherwise put
--find-links=requirements
in compiled `requirements.txt.The text was updated successfully, but these errors were encountered: