Skip to content

FIX: bug in np.where and recarray swapping #395

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

Merged
merged 1 commit into from
Aug 31, 2012
Merged

Conversation

certik
Copy link
Contributor

@certik certik commented Aug 30, 2012

Fixes #369 and the Ticket 2185

Fixes numpy#369 and the Ticket 2185

Thanks to @seberg for providing the patch.
@travisbot
Copy link

This pull request passes (merged 6e82fd31 into 5c944b9).

@travisbot
Copy link

This pull request passes (merged ecbd938 into 5c944b9).

@njsmith
Copy link
Member

njsmith commented Aug 30, 2012

Looks sensible to me.

@@ -169,6 +169,34 @@ def test_endian_bool_indexing(self,level=rlevel):
assert_(np.all(a[ya] > 0.5))
assert_(np.all(b[yb] > 0.5))

def test_endian_where(self,level=rlevel):
"""GitHuB issue #369"""
net = np.zeros(3, dtype='>f4')
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if it matters or is the case. But it may be necessary to test both '>' and '<' for big-endian machines where I guess the singletons should be big endian? would be just a second net here and a second test below (unless there is a way to make net non-native).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would you mind sending a PR for this please? I am going to merge this issue now.

@certik
Copy link
Contributor Author

certik commented Aug 31, 2012

Got reviewed by @njsmith, merging.

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

Successfully merging this pull request may close these issues.

Bug in numpy.where
4 participants