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
Fix objectmode is/is not #857
Conversation
This looks good to me. |
return self.builder.call(fn, (lhs, rhs, lopid)) | ||
if opstr in ops: | ||
opid = ops.index(opstr) | ||
assert 0 <= opid < len(ops) |
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.
That assert is really pointless, IMHO.
Has this already been released? |
Given this was merged in 2014, yes, it's already been released in quite a few releases. |
@pitrou Thanks. It's kindda difficult to know what release to attribute each pull request to, unless you decided to use the 'Milestone' feature... ;-) |
For that, I recommend you use the release notes, which tend to be documented quite comprehensively: |
@pitrou much appreciated! |
User reported the error https://groups.google.com/a/continuum.io/forum/?utm_medium=email&utm_source=footer#!msg/numba-users/3KwP6FVakBs/NawO3DcJqHMJ
Reason:
is
andis not
were not handled in object mode.