Cannot build docs - ModuleNotFoundError: 'myst_nb.parser'

I’m trying to build the hvplot docs with nbsite build --what=html --output=builtdocs --org holoviz --project-name hvplot and getting the following:

Configuration error:
There is a programmable error in your configuration file:

Traceback (most recent call last):
 File "...miniconda3/envs/my_dev_env/lib/python3.9/site-packages/sphinx/config.py", line 347, in eval_config_file
  exec(code, namespace)
 File "...hvplot/doc/conf.py", line 6, in <module>
  from nbsite.shared_conf import *
 File "...miniconda3/envs/my_dev_env/lib/python3.9/site-packages/nbsite/shared_conf.py", line 9, in <module>
  from nbsite import nbbuild
 File "...miniconda3/envs/my_dev_env/lib/python3.9/site-packages/nbsite/nbbuild.py", line 37, in <module>
  from myst_nb.parser import nb_to_tokens, nb_output_to_disc, tokens_to_docutils
ModuleNotFoundError: No module named 'myst_nb.parser'

I’m using: myst-nb version 0.17.1 nbsite version 0.7.2a14

[maximlt]

Closing in favor of https://github.com/holoviz/hvplot/issues/1004 and https://github.com/holoviz/hvplot/issues/1003

[maximlt]

have you tried to build thumbnails recently on your M1?

I don’t have a M1 (yet). Last time I tried to get the thumbnails to be created, I remember it was a pain 😕 This is one very good reason why I’d like us to generate thumbnails for the galleries across HoloViz, to make it simpler to build the sites (and additionally that should make the gallery look better…).

If you want to install geckodriver, maybe you can try with brew? Or using x86 conda envs may work, I think Philipp and Jean-Luc have played around with that.

Starting from scratch with inspiration from the panel docs.yaml:

Better starting from hvPlot’s docs.yaml instead of Panel, the install commands aren’t necessarily consistent across the repos.

Some more explanation on the conda dance below:

• the first line is actually pretty dangerous to run as a user I think, as it’s going to remove the defaults channel from your ~/.condarc file. You can restore it with conda config --append channels defaults (assuming you only have one channel there, if you have more, you’ll have to remember how they were ordered).
• I’ve converged to doing stuff like that to set explicitly the channels, that really helps conda to solve and the subsequent conda install/create calls don’t need to specify what channels they need, they get it from the configuration. It’s sad I have to remove defaults from the global config but I really found no way to configure an environment so that it doesn’t use defaults. There may be a better way, maybe what I’ll suggest instead is to update pyctdev so that it uses --override-channels all the time, making sure no other user-defined channel is used.

conda config --remove channels defaults
conda config --env --remove channels defaults
conda config --env --append channels pyviz/label/dev --append channels conda-forge