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
Hey,
I was wondering if/how to update the website to reflect the changes to pyne repository's examples. For example some of the examples have been recently updated for jupyter notebook/python3 compatibility (right side of figure) and these changes have not been reflected in the pyne.github.com repository's examples (left side of figure).
Thank you
The text was updated successfully, but these errors were encountered:
Hi @KennellyT - the website typically changes when we have a release, and new docs get pushed out. We haven't had a release in a few months so it is probably overdue. @pyne/core @pyne/developers any thoughts?
Hello @scopatz, I've noticed that some of the tutorials in the PyNE documentation are outdated following the recent release. To address this, I've been working on a PR where I review and update the tutorials. I've already made numerous fixes, but there are a couple of notebooks that I skipped for now.
The first one is 08-diffusion.ipynb, which is incompatible with Python 3. It requires some modifications to work properly, so I decided to skip it for the time being.
The second notebook is 11-ensdf-processing.ipynb, which contains outdated link formats. I believe these links need to be updated, and that's why I chose to skip this notebook as well.
Let me know if you have any specific instructions or suggestions regarding these notebooks, or if there's anything else I can help with. Thank you!
Hey,
I was wondering if/how to update the website to reflect the changes to pyne repository's examples. For example some of the examples have been recently updated for jupyter notebook/python3 compatibility (right side of figure) and these changes have not been reflected in the pyne.github.com repository's examples (left side of figure).
Thank you
The text was updated successfully, but these errors were encountered: