You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
👋 I'm just starting to look through some of the code here with the eventual goal of replacing the astropy-tutorials build machinery with nbpages. I'm confused about the current design. It looks like the current setup procedure for a new repository that will depend on nbpages is to use cookiecutter to copy over relevant code from nbpages and set up a directory structure to put the notebooks in. Is this really necessary? I would find it more natural to allow the user to structure their notebooks however they want, install nbpages as a package, and run, e.g.,:
👋 I'm just starting to look through some of the code here with the eventual goal of replacing the astropy-tutorials build machinery with
nbpages
. I'm confused about the current design. It looks like the current setup procedure for a new repository that will depend onnbpages
is to usecookiecutter
to copy over relevant code fromnbpages
and set up a directory structure to put the notebooks in. Is this really necessary? I would find it more natural to allow the user to structure their notebooks however they want, installnbpages
as a package, and run, e.g.,:or something like that.
Could someone clarify the design decision here?
The text was updated successfully, but these errors were encountered: