# Some mistake when I test it after finish install python bindings, help me? **URL:** \ **Category:** Installing preCICE\ **Created:** [July 21, 2023, 12:50pm UTC](https://precice.discourse.group/t/some-mistake-when-i-test-it-after-finish-install-python-bindings-help-me/1499 "2023-07-21T12:50:46Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![ilovenili](https://yyz2.discourse-cdn.com/free1/user_avatar/precice.discourse.group/ilovenili/32/1663_2.png) [@ilovenili](https://precice.discourse.group/u/ilovenili)\ **Post date:** [July 21, 2023, 12:50pm UTC](https://precice.discourse.group/t/some-mistake-when-i-test-it-after-finish-install-python-bindings-help-me/1499/1 "2023-07-21T12:50:46Z")
I finished install python bindings, when I test it, mistake happened. (1) my test step,as follow: - step 1:download python bindings v2.5.0(because precice version is v2.5.0) - step 2: Open terminal in python bindings folder. - step 3: `$ python3 setup.py test` (2) my mistake is as followed: ```plaintext [DESKTOP-41G51H4:06765] Signal: Segmentation fault (11) [DESKTOP-41G51H4:06765] Signal code: Address not mapped (1) [DESKTOP-41G51H4:06765] Failing at address: 0x4f0 [DESKTOP-41G51H4:06765] [0] /lib/x86_64-linux-gnu/libc.so.6(+0x43090)[0x7f4480826090] [DESKTOP-41G51H4:06765] [1] /home/nili/python-bindings/cyprecice.cpython-38-x86_64-linux-gnu.so(+0x315bf)[0x7f447d1615bf] [DESKTOP-41G51H4:06765] [2] python3(_PyEval_EvalFrameDefault+0x859)[0x56b619] [DESKTOP-41G51H4:06765] [3] python3[0x50b07e] [DESKTOP-41G51H4:06765] [4] python3(_PyEval_EvalFrameDefault+0x72d)[0x56b4ed] [DESKTOP-41G51H4:06765] [5] python3(_PyFunction_Vectorcall+0x1b6)[0x5f6ce6] [DESKTOP-41G51H4:06765] [6] python3(_PyEval_EvalFrameDefault+0x859)[0x56b619] [DESKTOP-41G51H4:06765] [7] python3(_PyEval_EvalCodeWithName+0x26a)[0x5697da] [DESKTOP-41G51H4:06765] [8] python3(_PyFunction_Vectorcall+0x393)[0x5f6ec3] [DESKTOP-41G51H4:06765] [9] python3[0x50b17c] [DESKTOP-41G51H4:06765] [10] python3(PyObject_Call+0x62)[0x5f60b2] [DESKTOP-41G51H4:06765] [11] python3(_PyEval_EvalFrameDefault+0x1f3c)[0x56ccfc] [DESKTOP-41G51H4:06765] [12] python3(_PyEval_EvalCodeWithName+0x26a)[0x5697da] [DESKTOP-41G51H4:06765] [13] python3(_PyFunction_Vectorcall+0x393)[0x5f6ec3] [DESKTOP-41G51H4:06765] [14] python3[0x59d21e] [DESKTOP-41G51H4:06765] [15] python3(_PyObject_MakeTpCall+0x296)[0x5f7506] [DESKTOP-41G51H4:06765] [16] python3(_PyEval_EvalFrameDefault+0x59c7)[0x570787] [DESKTOP-41G51H4:06765] [17] python3(_PyEval_EvalCodeWithName+0x26a)[0x5697da] [DESKTOP-41G51H4:06765] [18] python3(_PyFunction_Vectorcall+0x393)[0x5f6ec3] [DESKTOP-41G51H4:06765] [19] python3[0x50b17c] [DESKTOP-41G51H4:06765] [20] python3(PyObject_Call+0x62)[0x5f60b2] [DESKTOP-41G51H4:06765] [21] python3(_PyEval_EvalFrameDefault+0x1f3c)[0x56ccfc] [DESKTOP-41G51H4:06765] [22] python3(_PyEval_EvalCodeWithName+0x26a)[0x5697da] [DESKTOP-41G51H4:06765] [23] python3(_PyFunction_Vectorcall+0x393)[0x5f6ec3] [DESKTOP-41G51H4:06765] [24] python3[0x59d21e] [DESKTOP-41G51H4:06765] [25] python3(_PyObject_MakeTpCall+0x296)[0x5f7506] [DESKTOP-41G51H4:06765] [26] python3(_PyEval_EvalFrameDefault+0x59c7)[0x570787] [DESKTOP-41G51H4:06765] [27] python3(_PyEval_EvalCodeWithName+0x26a)[0x5697da] [DESKTOP-41G51H4:06765] [28] python3(_PyFunction_Vectorcall+0x393)[0x5f6ec3] [DESKTOP-41G51H4:06765] [29] python3[0x50b17c] [DESKTOP-41G51H4:06765] ***End of error message*** Segmentation fault ``` can you help me? ---
**Author:** ![IshaanDesai](https://yyz2.discourse-cdn.com/free1/user_avatar/precice.discourse.group/ishaandesai/32/1048_2.png) [@IshaanDesai](https://precice.discourse.group/u/IshaanDesai)\ **Post date:** [July 21, 2023, 6:14pm UTC](https://precice.discourse.group/t/some-mistake-when-i-test-it-after-finish-install-python-bindings-help-me/1499/2 "2023-07-21T18:14:39Z")
Hi @ilovenili We have observed this segmentation fault for pyprecice v2.5.0.2 just a few days ago! We are still trying to figure out what is going wrong. Initial investigation is showing that something is wrong in the `initialize_data()` function, but I am not yet sure. @BenjaminRodenberg it appears we are not the only ones observing the segmentation fault. ---
**Author:** ![ilovenili](https://yyz2.discourse-cdn.com/free1/user_avatar/precice.discourse.group/ilovenili/32/1663_2.png) [@ilovenili](https://precice.discourse.group/u/ilovenili)\ **Post date:** [July 22, 2023, 1:30am UTC](https://precice.discourse.group/t/some-mistake-when-i-test-it-after-finish-install-python-bindings-help-me/1499/3 "2023-07-22T01:30:38Z")
@IshaanDesai thanks, if mistake done, don’t forgeot tell me ---
**Author:** ![IshaanDesai](https://yyz2.discourse-cdn.com/free1/user_avatar/precice.discourse.group/ishaandesai/32/1048_2.png) [@IshaanDesai](https://precice.discourse.group/u/IshaanDesai)\ **Post date:** [July 25, 2023, 11:34am UTC](https://precice.discourse.group/t/some-mistake-when-i-test-it-after-finish-install-python-bindings-help-me/1499/4 "2023-07-25T11:34:49Z")
Hi @ilovenili We have found out that the Python bindings `v2.5.0.2` are not compatible with the latest release of Cython v3.0.0, which was released just last week. If you downgrade Cython using the command: ```bash pip install "cython<3" ``` the bindings should work again. We are trying to find out the incompatibility and will publish a compatibility release soon. ---
**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/precice/original/1X/67d2a5fa6f80e597e2267ff17fa8c1673cd11caa.svg) [@system](https://precice.discourse.group/u/system)\ **Post date:** [July 28, 2023, 11:35am UTC](https://precice.discourse.group/t/some-mistake-when-i-test-it-after-finish-install-python-bindings-help-me/1499/5 "2023-07-28T11:35:15Z")
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.