requirements.txt and runtime.txt are not followed if environment.yaml is present
See original GitHub issueIn https://github.com/simonsfoundation/regulatory_network_examples the requirements.txt and runtime.txt were not being observed. In https://github.com/simonsfoundation/jp_svg_canvas they are observed. The only difference I can see is that https://github.com/simonsfoundation/jp_svg_canvas has a setup.py script.
I could work around by adding python=2 to environment.yml and adding
pip install -r requirements.txt
to the postBuild script.
In my view these work arounds should not be needed.
Issue Analytics
- State:
- Created 6 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
requirements.txt and runtime.txt are not followed if ... - GitHub
Ok, I'm fine with not using requirements.txt if you have environment.yml as long as the restriction is documented. I find it confusing to...
Read more >Configuration Files — Binder 0.1b documentation
This specifies a list of Python packages that should be installed in your environment. Our requirements.txt example on GitHub shows a typical requirements ......
Read more >pip installing environment.yml as if it's a requirements.txt
I've implemented what Brian suggests in his comment. This converts the environment.yaml to requirements.txt :
Read more >Python Buildpack | Cloud Foundry Docs
The Python buildpack supports dependency installation using PIP when a requirements. txt file is included at the top level of your app's ...
Read more >Use requirements.txt | PyCharm Documentation - JetBrains
From the Tools menu, select Sync Python Requirements. In the opened dialog, specify the name of the requirements file. The recommended name for ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
yep!
or we could error on detection of both environment.yml and reqs.txt. I foresee people getting confused over this since it’s a bit hard to catch in the logs (esp since they don’t persist after the binder is built). If we had an informative error message telling people to use the
pip:
field maybe that’d help