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

Explore leveraging pytest's --tb=native command line option #26

Open
joshuadavidthomas opened this issue Mar 3, 2022 · 1 comment
Open

Comments

@joshuadavidthomas
Copy link
Collaborator

A custom rich console renderer was implemented because Rich's builtin Traceback requires a traceback object which pytest's test reports don't provide.

However, if you run with the command line option --tb=native, the actual traceback is printed, so I wonder if it would be worth it see if we could leverage that to be able to use the builtin Traceback instead of maintaining a custom version.

@bhavaniravi
Copy link
Contributor

Is it possible to create a custom Traceback class from whatever pytest provides?

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

2 participants