-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
REF: re-raise AssertionError unchanged #28959
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
Conversation
@@ -251,6 +251,8 @@ def aggregate(self, func=None, *args, **kwargs): | |||
|
|||
try: | |||
return self._python_agg_general(func, *args, **kwargs) | |||
except AssertionError: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm what's the point of the bare raise here? I get needed to differentiate now from the except Exception
, but coupled with change above is there something actually throwing the AssertionError
? Or do we mean to be catching ValueError
here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but coupled with change above is there something actually throwing the AssertionError
No, which means that during development we can now add assertions and not have them get swallowed.
lgtm. pls rebase |
rebased+green |
Thanks @jbrockmendel |
This should be all the remaining places where we catch
Exception
in groupby/apply/resample code. This should make debugging much easier going forward.cc @jreback @WillAyd