install fails with github version of cpython and pip about mitmproxy HOT 4 CLOSED

On Thu, Jan 4, 2024, 20:14 John Comeau ***@***.***> wrote: Problem Description A clear and concise description of what the bug is. python3 -m pip install mitmproxy fails with an ImportError while "Collecting zstandard..." Steps to reproduce the behavior: 1. git clone https://github.com/python/cpython && cd cpython 2. mkdir -p /tmp/cpython/{bin,usr,share} && ./configure --prefix= /tmp/cpython 3. make && make install 4. ~/tmp/cpython/bin/python3 -m pip install mitmproxy System Information Paste the output of "mitmproxy --version" here. It didn't install. But I have the Debian package installed, which outputs: Mitmproxy: 8.1.1 Python: 3.11.7 OpenSSL: OpenSSL 3.0.11 19 Sep 2023 Platform: Linux-5.19.0-2-amd64-x86_64-with-glibc2.36 Here is the specific error from the pip output, skipping the successful intermediate steps: Collecting zstandard<0.23,>=0.11 (from mitmproxy) Downloading zstandard-0.22.0.tar.gz (660 kB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 660.7/660.7 kB 6.0 MB/s eta 0:00:00 Installing build dependencies ... done Getting requirements to build wheel ... error error: subprocess-exited-with-error × Getting requirements to build wheel did not run successfully. │ exit code: 1 ╰─> [31 lines of output] <string>:37: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead. <string>:38: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead. Traceback (most recent call last): File "/home/jcomeau/tmp/cpython/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module> main() ~~~~^^ File "/home/jcomeau/tmp/cpython/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main json_out['return_val'] = hook(**hook_input['kwargs']) ~~~~^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/jcomeau/tmp/cpython/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel return hook(config_settings) ~~~~^^^^^^^^^^^^^^^^^ File "/tmp/pip-build-env-5m097oc2/overlay/lib/python3.13/site-packages/setuptools/build_meta.py", line 355, in get_requires_for_build_wheel return self._get_build_requires(config_settings, requirements=['wheel']) ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/tmp/pip-build-env-5m097oc2/overlay/lib/python3.13/site-packages/setuptools/build_meta.py", line 325, in _get_build_requires self.run_setup() ~~~~~~~~~~~~~~^^ File "/tmp/pip-build-env-5m097oc2/overlay/lib/python3.13/site-packages/setuptools/build_meta.py", line 507, in run_setup super(_BuildMetaLegacyBackend, self).run_setup(setup_script=setup_script) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/tmp/pip-build-env-5m097oc2/overlay/lib/python3.13/site-packages/setuptools/build_meta.py", line 341, in run_setup exec(code, locals()) ~~~~^^^^^^^^^^^^^^^^ File "<string>", line 106, in <module> File "/tmp/pip-install-wcb7xgyi/zstandard_58a2f4368f5b4874b15fbc8ad7d63c7e/make_cffi.py", line 161, in <module> ffi = cffi.FFI() ~~~~~~~~^^ File "/tmp/pip-build-env-5m097oc2/overlay/lib/python3.13/site-packages/cffi/api.py", line 48, in __init__ import _cffi_backend as backend ImportError: /tmp/pip-build-env-5m097oc2/overlay/lib/python3.13/site-packages/_cffi_backend.cpython-313-x86_64-linux-gnu.so: undefined symbol: _PyErr_WriteUnraisableMsg [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: subprocess-exited-with-error × Getting requirements to build wheel did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. — Reply to this email directly, view it on GitHub <#6582>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHY2PUSM3CW4PCPECFHG43YM35RJAVCNFSM6AAAAABBNMRBA2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGA3DMMRQGEYDANQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>