[issue19471] pandas DataFrame access results in segfault

2013-11-01 Thread Ned Deily
Ned Deily added the comment: Googling around a bit, there was another report of this problem that includes OS X crash stack traces. The crash there occurred in umath.so, a part of Numpy and that leads to a now-resolved bug in Numpy. https://github.com/pydata/pandas/issues/5396 https://github.

[issue19471] pandas DataFrame access results in segfault

2013-11-01 Thread Ned Deily
Ned Deily added the comment: No, this does not fit the signature of Issue18458, which is fixed in 2.7.6rc1 anyway. On the other hand, it is not likely that this is a problem in Python or its standard library. Pandas uses numpy and other third-party packages that contain C code. It's much mo

[issue19471] pandas DataFrame access results in segfault

2013-11-01 Thread Ezio Melotti
Ezio Melotti added the comment: This is probably a duplicate of #18458. -- nosy: +ezio.melotti, ned.deily, ronaldoussoren resolution: -> duplicate stage: -> committed/rejected status: open -> closed superseder: -> interactive interpreter crashes and test_readline fails on OS X 10.9 M

[issue19471] pandas DataFrame access results in segfault

2013-11-01 Thread Russell Jurney
New submission from Russell Jurney: Python 2.7.6 RC1 on Mac OS X Mavericks 10.9 results in segfault when accessing a Pandas DataFrame. Same problem as in 2.7.5. See http://stackoverflow.com/questions/19722580/segfault-with-pandas-with-python-v2-7-6-rc1-on-mac-os-x-10-9 -- messages: 20