Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better Traceback/StackTrace #364

Open
awilliamson opened this issue Sep 4, 2015 · 0 comments
Open

Better Traceback/StackTrace #364

awilliamson opened this issue Sep 4, 2015 · 0 comments

Comments

@awilliamson
Copy link
Member

Traceback returns a string, it's horrible, and only so much we can display from a single string.
I found the following:
https://github.com/ignacio/StackTracePlus

which provides a much nicer stack trace, and also advanced options such as adding known functions etc, which could be useful for SF-space erroring in the future.

The only thing which we can't implement is the io, everything else should be runnable. As we're using 5.1, this will work as we can't call the new 5.2/5.3 version of traceback ( which is stated as being hard to override as it's internal ).

Thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant