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

Display full Tracebacks instead of just exception error message. #50

Open
bpw opened this issue Mar 27, 2017 · 0 comments
Open

Display full Tracebacks instead of just exception error message. #50

bpw opened this issue Mar 27, 2017 · 0 comments

Comments

@bpw
Copy link
Member

bpw commented Mar 27, 2017

Seems like when student code crashes on tests, the output presentation shows just the exception message, but not the Traceback. Hopefully displaying the Traceback is just a matter of an extra method call.

Tracebacks in the output would be effective to help students get used to reading useful error messages and acting on hypotheses and evidence rather than "it didn't work, let's change this." They could just run the same test manually, but (a) a lower barrier to entry makes them more likely to try interpreting the error message and (b) sometimes there are subtle difference in environment (bindings from REPL history) that slow the manual re-testing process and confuse students.

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

No branches or pull requests

1 participant