-
-
Notifications
You must be signed in to change notification settings - Fork 397
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
Bug: exception representation swallows errors #188
Comments
Go ahead |
Oh, OK - nice catch.. I suppose I should have checked before throwing pytest under bus like that 😆 |
Another thing we need to take care when doing this is to support headers being passed to exception, as is done in @Bobronium will you be taking over this issue? |
@peterschutt, yep, I'm working on it. Though it may take a couple of days or even weeks, since I'm a bit more busy with life right now :) I'm fighting with backwards/cross compatibility with |
Ok, so I've been working on this for couple of days, but struggling to continue. If anyone wants to pick up on this, please let me know. I'm still committed to do this, but don't want to stop anyone who's able to do it quicker than me. If no one will pick this up, there's a great chance I will do it some time later. |
Ok, thanks for your efforts @Bobronium |
From #174 (comment):
Turns out, It's not pytest, it's actually starlite :)
StarLiteException
eats exception args, doesn't pass them toException
and doesn't define custom__str__
While
__repr__
is defined, that not what python uses to display errors.My proposal: ditch custom
__repr__
altogether and rely onException.args
.And make
detail
a property ofargs
joined together (which is actually justException.__str__
)The text was updated successfully, but these errors were encountered: