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
This came up during PlasmaPy/PlasmaPy-Tutorials#16 and a bit during PlasmaPy/PlasmaPy-Tutorials#17. Basically, working with the sphinx-gallery .py file format is more painful than working with notebooks, and I think we need to do everything we can to ease the example submission process.
There are a few ways I see that we could take here:
have a script that converts notebooks to .py once the PR is done, use it before merging example-adding PR - doesn't help with review, though that can be bypassed by simply pushing simple changes to notebooks instead of doing reviews (more or less limits example review to maintainers)
maybe even have a bot that does that to every commit adding a new file to examples
Opinions, gentlefolks? 😃
Other things I have stumbled upon while searching:
Indeed dealing with notebook in github with plain text is not easy. An inconvenient of notebooks is that they rapidly increase the repository size. On scikit-rf, the good practice is to pull "empty" notebooks, for this reason of size. Then the html documentation is built with sphinx from the notebooks.
That's an interesting idea, I'll have to look into that...
This came up during PlasmaPy/PlasmaPy-Tutorials#16 and a bit during PlasmaPy/PlasmaPy-Tutorials#17. Basically, working with the sphinx-gallery .py file format is more painful than working with notebooks, and I think we need to do everything we can to ease the example submission process.
There are a few ways I see that we could take here:
examples
Opinions, gentlefolks? 😃
Other things I have stumbled upon while searching:
The text was updated successfully, but these errors were encountered: