Closed jarmarshall closed 5 years ago
Binder is here using Python 3.7, which we've never tested with, and the build fails when trying to build an old scipy (see #63 for why we pin scipy). The quick fix would be to force Binder to use Python 3.6 (need to determine how to do this) but in the long term we want MuMoT to work with Python >=3.7 and more recent versions of scipy.
Thanks - I guessed it was some upgrade on Binder - looks like the solution might be here: https://mybinder.readthedocs.io/en/latest/config_files.html#config-files ?
"You can also specify which Python version to install in your built environment with environment.yml. By default, repo2docker installs |default_python| with your environment.yml unless you include the version of Python in this file. conda supports all versions of Python, though repo2docker support is best with Python 3.7, 3.6, 3.5 and 2.7."
PS I'm hoping with the RSE development funds we'll be able to work with on improving compatibility...
Added a runtime.txt
in PR #314 to force the use of Python 3.6. We can test this via https://mybinder.org/ prior to merging by pointing mybinder at the repo and feature branch associated with this PR.
Fixed via PR #314
Thanks for the rapid fix @willfurnass
Did this work on your branch before you merged the PR? On the master branch now I've managed to build (log available if useful), but then the server doesn't launch (Failed to connect to event stream
) and relaunching finds the built image, but then fails with Internal server error
Addendum: this may just be an availability issue, as I'm now waiting for a server to launch...
Great, can confirm this is working for master
branch now - thanks @willfurnass
The build on MyBinder has failed repeatedly for the latest version on the
master
branch, apparently for a variety of reasons. Most recent failed build log attached.