Add output log file for `cues`
@keeble is already working on this.
Since Feb 21, 2023.
Assessment
This issue has not been assessed yet.
Description
Currently cues only prints out the results of the inspection on the terminal, Mark W mentioned it would be nice to have the possibility to save this information.
- Add a
-ooption to the parser. - Save a copy of the printed out
cuesoutput in a log file.
In the first instance, it's probably just enough to open a file in a context message and write the printed out lines to it.
But, this might also be a good starting point to look into adding a bit of logging to the code (see #30 ).
- Dominant language
- Python
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DiamondLightSource/python-tristan
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
DiamondLightSource/python-tristan#57 · 1 comment · 1 assignee ·
All issues in DiamondLightSource/python-tristan
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100