Open maximlt opened 1 year ago
are you going to pin nbsite?
I haven't yet decided actually. There's some work required first anyway so that the projects don't all have to include some (quite a lot actually) of boiler plate, that includes CSS and template files. When this is done it'll be much easier to decide how to proceed.
One difficulty with NBSite and the pyviz channels is that it's not super easy to experiment building a single site with a new dev version of NBSite. Most projects use the pyviz/label/dev
channel to build their site. They've added it because at some point they either needed a dev version of another HoloViz package or a dev version of a HoloViz tool (pyct, pyctdev, nbsite, nbsmoke, ...). This kind of change is usually not reverted. So when a new dev release of NBSite (or any other HoloViz package really) is made all the other projects are affected. Unless they've added pins, but maintaining these pins is tedious.
I think we could/should actually create a pyviz channels called tools and tools-dev and push new versions of the tools there instead of on pyviz/label/main and pyviz/label/dev. That would allow for more granularity and decoupling the main packages from the tools.
A normal doc build would rely on pyviz/label/main
and on pyviz/label/tools
. I think the Github actions could be set up so that as a developer you could manually choose whether the action should pull the tools from pyviz/label/tools
or from pyviz/label/tools-dev
. The workflow I'm thinking of would be:
pyviz/label/tools-dev
pyviz/label/tools-dev
I'll credit @jlstevens for the idea of using other channels, I think it's a pretty decent workflow.
The HoloViz sites should be built using the same version of nbsite, pydata_sphinx and Python.
nbsite:
pydata-sphinx-theme:
Python:
EDIT
I just saw that Param was pinning 'myst_nb ==0.12.2' so it's worth checking if other sites do that too.
Updates: