-
-
Notifications
You must be signed in to change notification settings - Fork 18.9k
Closed
Labels
BugNeeds InfoClarification about behavior needed to assess issueClarification about behavior needed to assess issueOS XRelated to Mac OS & hardware issues (M1)Related to Mac OS & hardware issues (M1)
Description
Pandas version checks
-
I have checked that this issue has not already been reported.
-
I have confirmed this bug exists on the latest version of pandas.
-
I have confirmed this bug exists on the main branch of pandas.
Reproducible Example
from pandas import DataFrame
Issue Description
I tried to import pandas but it's straight to segmentation fault. Numpy can be imported separately. Installed by pip in venv and no other pandas installation exists.
Below is the backtrace from lldb.
(lldb) target create "python"
Current executable set to 'python' (x86_64).
(lldb) settings set -- target.run-args "-c" "import pandas as pd"
(lldb) r
Process 57543 launched: '/.venv/bin/python' (x86_64)
Process 57543 stopped
* thread #2, stop reason = exec
frame #0: 0x0000000100011000 dyld`_dyld_start
dyld`_dyld_start:
-> 0x100011000 <+0>: popq %rdi
0x100011001 <+1>: pushq $0x0
0x100011003 <+3>: movq %rsp, %rbp
0x100011006 <+6>: andq $-0x10, %rsp
Target 0: (Python) stopped.
(lldb) bt
* thread #2, stop reason = exec
* frame #0: 0x0000000100011000 dyld`_dyld_start
(lldb)
System Version: macOS 11.7.6 (20G1231)
Kernel Version: Darwin 20.6.0
Model Name: MacBook Pro
Model Identifier: MacBookPro11,1
Python: 3.12.2
Expected Behavior
No segmentation fault
Installed Versions
I can't even import it but pip said it's 2.2.2
Metadata
Metadata
Assignees
Labels
BugNeeds InfoClarification about behavior needed to assess issueClarification about behavior needed to assess issueOS XRelated to Mac OS & hardware issues (M1)Related to Mac OS & hardware issues (M1)