Numpy 1.9 on my Centos build chops int64s into two int32s #11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This bug fixes some problems I'm seeing on our Linux build. I'm not sure if this is a change in behavior in Numpy 1.9 or is something caused by differences in the way the arrays are built. The basic problem is this construct:
The problem is that "view" looks at the buffer,
(0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,)
and looks at the dtype which is two integers at four bytes apiece and carves the 16 bytes above into two 8 byte rows. The solution is to explicitly type arrays as numpy.int32 when this construct is used.