Skip to content

Unexpected result/segmentation fault with .ix/.loc (0.12.0) #4619

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

Closed
gdraps opened this issue Aug 21, 2013 · 1 comment · Fixed by #4622
Closed

Unexpected result/segmentation fault with .ix/.loc (0.12.0) #4619

gdraps opened this issue Aug 21, 2013 · 1 comment · Fixed by #4622
Labels
Bug Indexing Related to indexing on series/frames, not to indexes themselves
Milestone

Comments

@gdraps
Copy link
Contributor

gdraps commented Aug 21, 2013

Hitting a seg fault on a specific usage of .ix/.loc with release 0.12.0 (and current master). Any help is greatly appreciated. Let me know if I can provide any more info.

Here's an example produced with pandas 0.12.0 and numpy 1.7.1.

>>> df = pd.DataFrame({"A": [0, 1, 2]})
>>> print df.ix[[0,8,0]]  # unexpected results
              A
0  0.000000e+00
8           NaN
0  4.677219e+12
>>> df = pd.DataFrame({"A": list('abc')})
>>> print df.ix[[0,8,0]]
Segmentation fault (core dumped)

(.loc in place of .ix fails in the same way)

For comparison, here's the behavior with 0.11.0:

>>> df = pd.DataFrame({"A": [0, 1, 2]})
>>> print df.ix[[0,8,0]]
    A
0   0
8 NaN
0   0
>>> df = pd.DataFrame({"A": list('abc')})
>>> print df.ix[[0,8,0]]
     A
0    a
8  NaN
0    a

System info

i686 GNU/Linux

Python info

Python 2.7.3 (default, Apr 10 2013, 05:09:49) 
[GCC 4.7.2] on linux2
@jreback
Copy link
Contributor

jreback commented Aug 21, 2013

fixed in #4622

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Indexing Related to indexing on series/frames, not to indexes themselves
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants