Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Colormap byteorder bug #1095

Merged
merged 4 commits into from Aug 17, 2012

Conversation

Projects
None yet
2 participants
Owner

efiring commented Aug 16, 2012

Closes #1005.
I considered trying to work around the underlying putmask problem by modifying our _putmask, but concluded this was more trouble than it was worth; the bug seems to involve only the most special and obscure circumstances, which we happened to be triggering when substituting the number slightly less than unity for values of 1.0, and only when the input byte order is not native.
The solution in this pull request is to change the byte order to native before proceding with the putmask and other calculations in the Colormap.call() method

Owner

mdboom commented Aug 17, 2012

+1

@efiring efiring added a commit that referenced this pull request Aug 17, 2012

@efiring efiring Merge pull request #1095 from efiring/colormap_byteorder_bug
Colormap byteorder bug
f927517

@efiring efiring merged commit f927517 into matplotlib:master Aug 17, 2012

@efiring efiring deleted the efiring:colormap_byteorder_bug branch May 29, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment