Title says it all. I wanted to test out building on pre-execeuted notebooks to circumvent a few other issues I'd encountered. Config fragment is
#######################################################################################
# Execution settings
execute:
execute_notebooks : off
cache : ""
exclude_patterns : []
And produces the following output
$ jupyter-book build .
Running Sphinx v2.4.4
loading pickled environment... done
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 1 source files that are out of date
updating environment: WARNING: Conf jupyter_execute_notebooks can either be `force`, `auto`, `cache` or `off`
without to do any doc build.
I suspect you might need to replace off with 'off'. Check out the documentation here.
Thanks! Probably worth making this more explicit in the comments of the example docs here: https://jupyterbook.org/customize/config.html#configuration-reference

does anybody know what this weird YAML bug is? It's so annoying lol
Haha agreed, this is super annoying - really enjoyed the meme above.
The worst part is that auto works without quotes or ticks and off doesn't work unless it's surrounded by single quotes: 'off'.
The error/warning message recommends backticks:
updating environment: WARNING: Conf jupyter_execute_notebooks can either be `force`, `auto`, `cache` or `off`
and the docs recommend double quotes: "off"
@firasm can you try upgrading to the latest jupyter book and try again? I actually just special-cased off so it should work now. (the problem is that YAML treats off as false which is why you have to add a string)
Nice, confirmed.
Updating to 0.7.0b4 fixes the issue above. For anyone seeing this, to update*:
pip install "jupyter-book>=0.7.0b4"
Issue can probably be closed now.
(*P.S. b3 and b4 aren't listed on the releases page yet)
Oops, good call re: releases. Will close this one and add releases!
Most helpful comment
@firasm can you try upgrading to the latest jupyter book and try again? I actually just special-cased
offso it should work now. (the problem is that YAML treatsoffasfalsewhich is why you have to add a string)