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

Print traceback before proceeding to search for answers #53

Closed
briancohan opened this issue Jul 14, 2021 · 2 comments
Closed

Print traceback before proceeding to search for answers #53

briancohan opened this issue Jul 14, 2021 · 2 comments
Assignees
Projects

Comments

@briancohan
Copy link
Contributor

In the main loop, we should probably print the full traceback (before going to stackoverflow) to the terminal so that they still get the stack trace even if our logic crashes. This would also allow the traceback to be visible if they exit the application.

@briancohan briancohan added this to Backlog in Code Jam via automation Jul 14, 2021
@mustafaquraish
Copy link
Contributor

Well the workflow in my mind is that:

  1. User runs their program through python, and sees the exception / traceback
  2. User then runs the program through pytui.

So in reality they will already have the traceback on their terminal beforehand. We should add the ability to show the traceback inside the user interface in a separate panel (I believe @ethansocal was showing this during a code standup?). That would be more useful IMO

@briancohan
Copy link
Contributor Author

In my mind, if you call our app in lieu of python and there are no errors, then you should not see anything different. With the slight exception that we could use rich.print to make it look nicer.

VagishVela added a commit that referenced this issue Jul 16, 2021
trackeback prints regardless of entering UI #53
Code Jam automation moved this from Backlog to Complete Jul 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Code Jam
Complete
Development

No branches or pull requests

3 participants