8000 BUG: Fix randint when range is 2**32 by bashtage · Pull Request #14501 · numpy/numpy · GitHub
[go: up one dir, main page]

Skip to content

BUG: Fix randint when range is 2**32 #14501

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 15, 2019
Merged

Conversation

bashtage
Copy link
Contributor

Fix randint to use 32-bit path when range is exactly 2**32

closes #14189

@bashtage bashtage force-pushed the bug-randint branch 2 times, most recently from 2d1248a to 7d43968 Compare September 13, 2019 22:13
@charris charris added this to the 1.17.3 release milestone Sep 13, 2019
@charris
Copy link
Member
charris commented Sep 13, 2019

This only affects 1.17.x, correct?

@bashtage
Copy link
Contributor Author
bashtage commented Sep 13, 2019 via email

@mattip
Copy link
Member
mattip commented Sep 14, 2019

minor nit in formatting, otherwise LTGM. Will merge soon even without the formatting fix, it seems we will have to carefully check the release note rendering anyway.

Fix randint to use 32-bit path when range is exactly 2**32

closes numpy#14189
@mattip mattip merged commit e4de01d into numpy:master Sep 15, 2019
@mattip
Copy link
Member
mattip commented Sep 15, 2019

Thanks @bashtage

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.

Legacy randint with low=2**32 does not reproduce NumPy <1.17 values
3 participants
0