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

Exclude pyvows and preggy from tracebacks #96

Open
Zearin opened this issue Jul 19, 2013 · 0 comments
Open

Exclude pyvows and preggy from tracebacks #96

Zearin opened this issue Jul 19, 2013 · 0 comments
Labels

Comments

@Zearin
Copy link
Collaborator

Zearin commented Jul 19, 2013

When a vow is broken, it prints a traceback. Overall, this is useful information. But the traceback also includes information about how pyvows (and/or preggy) handled the error.

In most cases, this information isn't useful to the person reading the traceback. It just adds noise for the user to sift through, instead of helping them pinpoint why the vow was broken.

Recommendations

I have two ideas for improving this:

  • color-code the pyvows/preggy parts of the traceback differently (perhaps with the ANSI code for “dim” text)
  • exclude the pyvows/preggy parts of the traceback, unless the user is using -vvvv; (or, perhaps, offer a separate --debug option to toggle the visibility of these portions of the traceback)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant