Closed emiliom closed 1 year ago
Check out this pull request on
See visual diffs & provide feedback on Jupyter Notebooks.
Powered by ReviewNB
Hmm, the CI PR deploy error occurred during mamba build:
Encountered problems while solving.
Problem: nothing provides requested echopype 0.6.4.1**
Error: The process '/usr/share/miniconda3/condabin/mamba' failed with exit code 1
I didn't have any problems building the env locally with mamba using the same binder/environment.yml
file. I'll look more closely at the error.
notebook1
, etc). This avoids a new problem that was happening due to the use ofglob(*.zarr)
, plus it keeps things tighter.nodefaults
channel, to prevent the silent use of thedefault
channel, which was leading to a numpy version (1.24.x) that was incompatible with numba. Now, the dependency incompatibility is gone (numpy 1.23.x is installed) w/o having to pin numpy, and a recent (latest?) version of numba is installed whereas a pretty old version was previously being installed. See https://github.com/movingpandas/movingpandas-examples/issues/22 and https://discourse.holoviz.org/t/datashader-import-fails-with-numba-error/5004/2jupyterbook
folder tonotebooks
folder, the same one where all the content is found. Renamed the files back to the default names,_config.yml
and_toc.yml
, so that the jupyterbook build statement can be simpler (no need to specify the path to those two config files). The file move was driven mainly by a new jupyterbook build error that seemed to be driven by the yml files being in a different folder as the content files. But it's something I've wanted to do before, for simplicity.jupyterbook
folder and to use the simplifiedjupyter-book build
statement.