Skip to content
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

BUG: Patch maybe_convert_objects uint64 handling #14951

Merged

Conversation

gfyoung
Copy link
Member

@gfyoung gfyoung commented Dec 22, 2016

Makes method robust against known numpy bug that you can't compare uint64 against int64
because they are casted to float64 during the comparison, causing truncation.

xref #14937.
Follow-up to #14916.

Makes method robust against known NumPy bug
that you can't compare uint64 against int64
because they are casted to float64 during
the comparison, causing truncation.
@codecov-io
Copy link

codecov-io commented Dec 22, 2016

Current coverage is 84.64% (diff: 100%)

Merging #14951 into master will not change coverage

@@             master     #14951   diff @@
==========================================
  Files           144        144          
  Lines         51021      51021          
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
  Hits          43188      43188          
  Misses         7833       7833          
  Partials          0          0          

Powered by Codecov. Last update f79bc7a...987ae5c

@jreback jreback added Bug Dtype Conversions Unexpected or buggy dtype conversions labels Dec 22, 2016
@jreback jreback added this to the 0.20.0 milestone Dec 22, 2016
@jreback jreback merged commit 868d114 into pandas-dev:master Dec 22, 2016
@jreback
Copy link
Contributor

jreback commented Dec 22, 2016

thanks!

@gfyoung gfyoung deleted the maybe-convert-objects-robust branch December 22, 2016 14:50
ShaharBental pushed a commit to ShaharBental/pandas that referenced this pull request Dec 26, 2016
Makes method robust against known NumPy bug
that you can't compare uint64 against int64
because they are casted to float64 during
the comparison, causing truncation.
jreback pushed a commit that referenced this pull request Jan 17, 2017
1) Introduces and propagates `UInt64Index`, an index specifically for
`uint`.  xref #14935    2) <strike> Patches bug from #14916 that makes
`maybe_convert_objects` robust against the known `numpy` bug that
`uint64` cannot be compared to `int64`.  This bug was caught during
testing of `UInt64Index`. </strike>    **UPDATE**: Patched in #14951

Author: gfyoung <gfyoung17@gmail.com>

Closes #14937 from gfyoung/create-uint64-index and squashes the following commits:

8ab6fbd [gfyoung] ENH: Create and propagate UInt64Index
AnkurDedania pushed a commit to AnkurDedania/pandas that referenced this pull request Mar 21, 2017
1) Introduces and propagates `UInt64Index`, an index specifically for
`uint`.  xref pandas-dev#14935    2) <strike> Patches bug from pandas-dev#14916 that makes
`maybe_convert_objects` robust against the known `numpy` bug that
`uint64` cannot be compared to `int64`.  This bug was caught during
testing of `UInt64Index`. </strike>    **UPDATE**: Patched in pandas-dev#14951

Author: gfyoung <gfyoung17@gmail.com>

Closes pandas-dev#14937 from gfyoung/create-uint64-index and squashes the following commits:

8ab6fbd [gfyoung] ENH: Create and propagate UInt64Index
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Dtype Conversions Unexpected or buggy dtype conversions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants