[issue40574] segfault causing regression from PEP 573 implementation (PyQt5)

Thomas Caswell added the comment: That seems reasonable. To be pedantic, it is pyqt5-sip (not sip) that was the source of the problem. I am going to open an issue with pip to disable caching locally built wheels for pre-released versions of Python. --

[issue40574] segfault causing regression from PEP 573 implementation (PyQt5)

Petr Viktorin added the comment: So, the failure is expected. Python's ABI can change until the 3.9.0 final release, so wheels built for different commits can be incompatible. This applies to alphas/betas as well, as you say. There is the PEP 384 stable ABI, which is much stricter (and more

[issue40574] segfault causing regression from PEP 573 implementation (PyQt5)

STINNER Victor added the comment: The stable ABI should not change between Python 3.8 and 3.9. In practice, it seems like something changed. But without any gdb traceback, I cannot tell what. I suggest to try again when beta1 will be released. The ABI should be way more stable after beta1.

[issue40574] segfault causing regression from PEP 573 implementation (PyQt5)

Thomas Caswell added the comment: The path is - on a commit prior to e1becf46b4e3ba6d7d32ebf4bbd3e0804766a423 install pyqt-sip. pip will build a wheel for you called PyQt5_sip-12.7.2-cp39-cp39-linux_x86_64.whl - on a commit after e1becf46b4e3ba6d7d32ebf4bbd3e0804766a423 if you do `pip

[issue40574] segfault causing regression from PEP 573 implementation (PyQt5)

STINNER Victor added the comment: > I think I have figured out the problem. I had a locally built and cached > wheel of PyQt5-sip from before PEP573 went in. If that wheel is used for > later commits I get the segfault, if I rebuilt the wheel from source it works. Hum, I'm not sure that I

[issue40574] segfault causing regression from PEP 573 implementation (PyQt5)

Thomas Caswell added the comment: I think I have figured out the problem. I had a locally built and cached wheel of PyQt5-sip from before PEP573 went in. If that wheel is used for later commits I get the segfault, if I rebuilt the wheel from source it works. I am not sure if this is an

[issue40574] segfault causing regression from PEP 573 implementation (PyQt5)

Thomas Caswell added the comment: The script I used for the bisect was: --- TARGET_ENV=bisect_env rm -r ~/.pybuild/$TARGET_ENV || true git clean -xfd ./configure --prefix=/home/tcaswell/.pybuild/$TARGET_ENV make -j 9 make install ~/.pybuild/$TARGET_ENV/bin/python3 -m venv --copies --clear

[issue40574] segfault causing regression from PEP 573 implementation (PyQt5)

Change by hai shi : -- nosy: +shihai1991 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40574] segfault causing regression from PEP 573 implementation (PyQt5)

STINNER Victor added the comment: I also with: ./configure --prefix=/opt/py39 --with-system-expat --with-system-ffi I still cannot reproduce the crash. I tested Python at commit 1c2fa781560608aa4be50c748d4b3f403cfa5035. I tested on Fedora 32 (GCC 10.0.1). $ /opt/py39/bin/python3.9 -m

[issue40574] segfault causing regression from PEP 573 implementation (PyQt5)

Change by STINNER Victor : -- title: segfault causing regression from PEP 573 implementation -> segfault causing regression from PEP 573 implementation (PyQt5) ___ Python tracker