Skip to content

BUG: Fix aradixsort indirect indexing. #14417

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
Sep 4, 2019

Conversation

hameerabbasi
Copy link
Contributor

Fixes #14413.

@eric-wieser
Copy link
Member

Let's make sure we fix this case too

@hameerabbasi
Copy link
Contributor Author

This fix fixes that case as well on my local machine.

@pytest.mark.parametrize('dtype',[
np.uint8, np.uint16, np.uint32, np.uint64,
np.int8, np.int16, np.int32, np.int64,
np.float16, np.float32, np.float64
Copy link
Member

Choose a reason for hiding this comment

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

Nice touch changing to the non-string names, thanks

@charris charris added this to the 1.17.2 release milestone Sep 4, 2019
@charris charris changed the title BUG: Fix lexsort + radix sort. BUG: Fix aradixsort indirect indexing. Sep 4, 2019
@charris
Copy link
Member

charris commented Sep 4, 2019

Shippable has been hung up for about 8 hours, so merging without. Thanks Hameer.

@charris charris merged commit 3f8d70e into numpy:master Sep 4, 2019
@hameerabbasi hameerabbasi deleted the lexsort-rsort-fix branch September 4, 2019 15:52
@charris charris added component: numpy._core and removed 09 - Backport-Candidate PRs tagged should be backported labels Sep 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Regression: lexsort gives wrong results on short integer types
3 participants