review the way traceback is printed when exception are raised
Open
Low Priority
- Dominant language
- Python
- Stars
- 18
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
currently the call we use e.g. in https://github.com/dmwm/CRABClient/blob/master/bin/crab#L197-L198 to print the traceback in crab.log also prints again the exception message.
This can be annoying when the message is long, like discussed in the PR comments around https://github.com/dmwm/CRABClient/pull/4684#issuecomment-289489045
Moreover in other places the traceback is printed using the =traceback= module from the standard library
Things could be harmonized to use same method and to avoid duplication of message.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.