PrettyErrors
PrettyErrors copied to clipboard
onelivesleft
Prettify Python exception output to make it legible.
This issue is the same as #39, unclear why it resurfaced. When pretty_errors is run as a module inside a pyenv virtualenv to add it to Python startup procedure (`python...
After installing PrettyErrors with `pip install pretty-errors` or with `python -m pip install pretty_errors` makes all .pyw files unusable. When i unistalled PrettyErrors .pyw files worked again.
It seems like there is a `display_locals` which will show local variables. This is very useful, but often functions are short and the exception can be easily understood by looking...
The stack trace pretty errors outputs is that of the main thread. Say I have a task in a thread pool that raises an AssertionError. pretty errors just outputs "AssertionError"....
Is it possible to have PrettyErrors handle exception outputs when using Python's pdb? I've used the following code to import PrettyErrors ``` import pretty_errors pretty_errors.replace_stderr() ``` but when adding breakpoints...
How hard would it be to make this work in JupyterLab? I tried it, but the regular JupyterLab exception style remains. I guess they do something similar where they intercept...
# Issue When printing a syntax error, the exception includes a help message in the `msg` attribute, but the message in `args[0]` is printed instead, which is almost always `"invalid...
It would be great to be sure that any change or addition does not break any existing use case... so adding a simple CI job running with several Python versions...
The most active fork I found is: https://github.com/Uchiha-Senju/PrettyErrors_modified
Metadata
Owner
Metadata
Prettify Python exception output to make it legible.