runtime and requirements in `binder/` doesn't work
See original GitHub issuevia @hydrosquall in #139:
With that said, this stops working if
runtime.txt
andrequirements.txt
are both under thebinder/
folder, so I had to get rid of thebinder/
folder and put both text files in the project root.It also doesn’t work if just
runtime.txt
is in the root andrequirements.txt
is in thebinder/
folder, since it will fail to install the python2 kernel. This might be a bug worth investigating separately.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
runtime and requirements in binder/ doesn't work #141 - GitHub
With that said, this stops working if runtime.txt and requirements.txt are both under the binder/ folder, so I had to get rid of...
Read more >Configuration Files — Binder 0.1b documentation
Sometimes you want to specify the version of the runtime (e.g. the version of Python or R), but the environment specification format will...
Read more >why is binder not finding a package? - python - Stack Overflow
Launches currently from the requirements binder repo example are only Python 3.8.12. See current version of runtime.txt.
Read more >Binder processing - IBM
You can always rebind if you don't require this additional processing. You can also re-bind if you used the ... Language Environment® run...
Read more >ASP.NET Core 3.1.0 site won't run - Could not load Microsoft ...
AspNetCore.Razor.Runtime, Version=3.1.1.0. I'm building an ASP.NET Core app, and it's stored on an Azure web ...
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
Fixed by #277.
This will be fixed in #277 I believe - we had a hard-coded path to a requirements file that was only in the Python2 buildpack, so would only be uncovered if people both had 2.7 specified in runtime.txt and used a
binder/
folder