45
0
Fork
You've already forked project-issues
0

Add deprecation notice on all old Jupyter notebooks and scripts #63

Open
opened 2026年06月22日 03:50:48 +02:00 by songtech-0912 · 1 comment

We have a lot of our simulations code in Jupyter notebooks and scripts, but many of these are redundant or no longer updated - something that isn't easy to tell by inspection for those who are not actively working on simulations. Since our membership isn't fixed, it is essential that we put deprecation notices on these notebooks/scripts that the notebooks/scripts represent past work that is possibly no longer up-to-date.

We have a lot of our simulations code in Jupyter notebooks and scripts, but many of these are redundant or no longer updated - something that isn't easy to tell by inspection for those who are not actively working on simulations. Since our membership isn't fixed, it is essential that we put deprecation notices on these notebooks/scripts that the notebooks/scripts represent past work that is possibly no longer up-to-date.
Author
Owner
Copy link

For deprecation notices, I think something like this (placed in a markdown block) should work work, in cases where we have a notebook that has been replaced by a more powerful script/library:

**IMPORTANT: This notebook is no longer updated. Please see `SomeUpdatedSimulation.py` for more up-to-date versions of the simulations in this notebook.**

Or if a simulation is completely archived and no longer relevant:

**IMPORTANT: This notebook is no longer updated and is kept for archival purposes only.**
For deprecation notices, I think something like this (placed in a markdown block) should work work, in cases where we have a notebook that has been replaced by a more powerful script/library: ```markdown **IMPORTANT: This notebook is no longer updated. Please see `SomeUpdatedSimulation.py` for more up-to-date versions of the simulations in this notebook.** ``` Or if a simulation is completely archived and no longer relevant: ```markdown **IMPORTANT: This notebook is no longer updated and is kept for archival purposes only.** ```
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
elaraproject/project-issues#63
Reference in a new issue
elaraproject/project-issues
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?