8000 Incorrect result for np.rint on Win32, numpy 1.10.1, MKL · Issue #6685 · numpy/numpy · GitHub
[go: up one dir, main page]
Skip to content

Incorrect result for np.rint on Win32, numpy 1.10.1, MKL #6685

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.

Sign up for GitHub

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

Jump to bottom
Closed
matthew-brett opened this issue Nov 14, 2015 · 3 comments
Closed

Incorrect result for np.rint on Win32, numpy 1.10.1, MKL #6685

matthew-brett opened this issue Nov 14, 2015 · 3 comments
Labels
00 - Bug component: numpy._core

Comments

@matthew-brett
Copy link
Contributor

Sorry for the specificity of this message, but I'm hoping it's the right place to file this.

With 32-bit numpy + MKL on Windows:

>>> import numpy as np
>>> ds = 4607998452777363968
>>> int(float(ds))
4607998452777363968L
>>> int(np.rint(ds))
4607998452777363456L

This is true of conda numpy packages and Christoph's wheels (though these seem to have disappeared now).
This was referenced Nov 14, 2015
Closed
Closed
matthew-brett added a commit to matthew-brett/numpy that referenced this issue Nov 18, 2015
@matthew-brett
TST: test np.rint bug for large integers
8d00317 
Test for numpy#6685

Add test to remind packagers that they may need to fix or workaround
this bug on some systems.
@matthew-brett matthew-brett mentioned this issue Nov 18, 2015
Merged
matthew-brett added a commit to matthew-brett/numpy that referenced this issue Nov 18, 2015
@matthew-brett
TST: test np.rint bug for large integers
ef96253 
Test for numpy#6685

Add test to remind packagers that they may need to fix or workaround
this bug on some systems.
@juliantaylor
Copy link
Contributor

might caused the lack of generics on those platforms

@njsmith njsmith mentioned this issue Dec 11, 2015
Closed
@matthew-brett matthew-brett mentioned this issue Jan 13, 2016
Closed
@gfyoung
Copy link
Contributor
gfyoung commented Jan 14, 2016

Either it's an issue with version '1.10.1' or an issue with one of those platforms, as I don't see this bug on my Windows32 machine.

Python 2.7.11 (v2.7.11:6d1b6a68f775, Dec  5 2015, 20:32:19) [MSC
Intel)] on win32
Type "help", "copyright", "credits" or "license" for more inform
>>> import numpy as np
>>> np.__version__
'1.10.2'
>>> ds = 4607998452777363968
>>> int(float(ds))
4607998452777363968L
>>> int(np.rint(ds))
4607998452777363968L

jaimefrio pushed a commit to jaimefrio/numpy that referenced this issue Mar 22, 2016
@matthew-brett @jaimefrio
TST: test np.rint bug for large integers
062b91c 
Test for numpy#6685

Add test to remind packagers that they may need to fix or workaround
this bug on some systems.
@matthew-brett matthew-brett mentioned this issue Apr 20, 2016
Merged
@thomastweets thomastweets mentioned this issue Jul 26, 2016
Open
@aixtools aixtools mentioned this issue Oct 23, 2016
Merged
@kalefranz kalefranz mentioned this issue May 9, 2017
Open
@mattip
Copy link
Member
mattip commented May 7, 2019

Closing, the corresponding issue in anaconda-issues is the correct place for this

@mattip mattip closed this as completed May 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
00 - Bug component: numpy._core
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@matthew-brett @charris @juliantaylor @mattip @gfyoung
0