[Python] Python fintech import makes macOS(Sequoia) to kill the process (EXC_BAD_ACCESS)

Discussão em 'Python' iniciado por Stack, Janeiro 24, 2025.

  1. Stack

    Stack Membro Participativo

    I have problem with fintech python package in Macbook running macOS(Sequoia). I am unable to import it. Package is installed with pip and it does say in the end that package is installed successfully.

    I get below in crash report


    Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid)) Exception Codes: UNKNOWN_0x32 at 0x0000000102fa8000 Exception Codes: 0x0000000000000032, 0x0000000102fa8000 Termination Reason: Namespace CODESIGNING, Code 2 Invalid Page
    ​

    when I just do the import I get below

    python -v -c "import fintech"


    .pyenv/versions/3.10.15/lib/python3.10/ctypes/pycache/_endian.cpython-310.pyc' import 'ctypes._endian' # <_frozen_importlib_external.SourceFileLoader object at 0x1023c6950> import 'ctypes' # <_frozen_importlib_external.SourceFileLoader object at 0x1023c4e20> .pyenv/versions/3.10.15/lib/python3.10/pycache/fnmatch.cpython-310.pyc matches .pyenv/versions/3.10.15/lib/python3.10/fnmatch.py .pyenv/versions/3.10.15/lib/python3.10/pycache/fnmatch.cpython-310.pyc' import 'fnmatch' # <_frozen_importlib_external.SourceFileLoader object at 0x1023c5540> import 'fintech.pytransform' # <_frozen_importlib_external.SourcelessFileLoader object at 0x1022c2440> zsh: killed python -v -c "import fintech"
    ​

    I tried different fintech packages and python versions 3.9 to 3.10 same error.

    Also did install/reinstall python with homebrew and later on with pyenv nothing works.

    If some can give me a clue, I will be thankful.

    I also tried signing of .pyenv but no success.

    Just for the context, I have setup development environment using pycharm for odoo 15 on Macbook, setup works fine, but unable to use account_ebics module which uses fintech python package. when I install the module I get below on log "Process finished with exit code 137 (interrupted by signal 9:SIGKILL)"

    Continue reading...

Compartilhe esta Página