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

[Python] Issue to install pyarrow and pandas together in a conda environment #41067

Closed
Mathias5 opened this issue Apr 8, 2024 · 5 comments
Closed

Comments

@Mathias5
Copy link

Mathias5 commented Apr 8, 2024

Describe the bug, including details regarding any error messages, version, and platform.

Hi,
since a few days when I create a conda environment with pyarrow and pandas, I get a segmentation fault when loading pandas.
To replicate:
conda create -n test python pyarrow pandas
conda activate test
python
import pandas

This leads to a segmentation fault.

Component(s)

Python

@jorisvandenbossche
Copy link
Member

Can you show the output of conda list? Do you see any traceback or error message besides "segmentation fault"?

This is probably a conda packaging issue.

@xshirax
Copy link

xshirax commented Apr 8, 2024

Hi. I believe the issue is related to new release of snappy 1.2.0
Similar issue is solved (for me) with snappy 1.1
I get same bug (segmentation fault). specifically:

File "/homes/.../.conda/envs/.../lib/python3.10/site-packages/pyarrow/init.py", line 65, in
import pyarrow.lib as _lib
ImportError: /homes/.../.conda/envs/.../lib/python3.10/site-packages/pyarrow/../../.././liborc.so: undefined symbol: _ZN6snappy11RawCompressEPKcmPcPm

@jorisvandenbossche jorisvandenbossche changed the title Issue to install pyarrow and pandas together in a conda environment [Python] Issue to install pyarrow and pandas together in a conda environment Apr 8, 2024
@jorisvandenbossche
Copy link
Member

If that was the issue, that should be solved now when recreating a fresh environment, see #41058

But, that issue should only have occurred since yesterday, and not for a "few days" (and it's also not a segmentation fault)

@Mathias5
Copy link
Author

Mathias5 commented Apr 8, 2024

Hi,
Indeed I think it started to happen yesterday and not "a few days ago" as I initially said.
And it did cause segmentation fault in my python env.
It seems like it has been resolved now, thanks for the update.

@Mathias5 Mathias5 closed this as completed Apr 8, 2024
@Mathias5
Copy link
Author

Mathias5 commented Apr 8, 2024

The issue has been resolved, see #41058

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

No branches or pull requests

3 participants