ISISNeutronMuon / ISISNeutronMuon/MDMC
Logging is notpossible through Jupyter notebooks
- Dominant language
- Python
- Stars
- 4
- Forks
- 0
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 5
Description
Jupyter doesn't play nicely with logging, and we do try to do some in our code. Asking the Scipp developers we would need to make our own handler for logging to output to the Jupyter cells:
Jan-Lukas Wynen:
AFAIK there is no way of logging to the Jupyter log console for security reasons. That console is only for javascript.
You can set a stream handler for your logger, that should show up in a notebook. In scipp, we use configure or configure_workflow from https://scipp.github.io/ess/generated/modules/ess.logging.html#module-ess.logging which build on top of https://scipp.github.io/generated/modules/scipp.logging.html#module-scipp.logging. We have a special widget that shows log messages. See https://scipp.github.io/reference/logging.html for a short guide.
Contributor guide
No contributing guide indexed for this repository
Research direction
No source files or tests are named. Start by reading the referenced ess.logging and scipp.logging documentation, especially configure and configure_workflow, and compare the existing special widget guidance. The intended result is a supported way for logging from MDMC code to appear in Jupyter notebook cells.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter, jupyter-notebook, python
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100