Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure Sphinx gallery to copy files from pynest/examples #3284

Merged
merged 3 commits into from
Aug 20, 2024

Conversation

jessica-mitchell
Copy link
Contributor

This PR adjusts the configuration for Sphinx gallery so it now copies additional files from pynest/examples.
This makes it easier to keep all files related to the example together and link to them appropriately.
This means the function for copying hpc_benchmark_connectivity.svg can be removed from conf.py

This also fixes #3246

Note however, files (txt, images etc) required for Python examples, need to be somehow linked to in the appropriate script. For eprop handwriting text file - it is added as a :download: link.
In the case of Sonata, there is an additional folder with many types of files. These are not copied and a direct link to the repo needs to be used. Sphinx gallery does not support >1 subfolders. (see mention here)
Thus, when creating Python scripts and additional data or image files need to be used, care must be taken that links are included.

@jessica-mitchell jessica-mitchell added S: Normal Handle this with default priority T: Maintenance Work to keep up the quality of the code and documentation. I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) labels Aug 8, 2024
Copy link
Contributor

@steffengraber steffengraber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@jessica-mitchell jessica-mitchell merged commit ba87440 into nest:master Aug 20, 2024
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority T: Maintenance Work to keep up the quality of the code and documentation.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Provide extra files needed to run examples on Read the Docs
2 participants