Free-threaded Python Library Compatibility Checker

Compatibility Results: CPython 3.13t and 3.14t

Library Installation Status Heatmap
Loading...

Loading library status heatmap...

Loading...

Loading Python 3.13t heatmap...

Loading...

Loading Python 3.14t heatmap...

Success
Failed
No Data

Python 3.13t Compatibility Results

Library Version Build Result Error Details Last Updated At
pytest-asyncio 1.3.0 Success - 2025-11-11 01:02:22
python-utils 3.9.1 Success - 2025-05-20 18:34:55
html5lib 1.1 Success - 2025-05-20 20:41:03
selenium 4.39.0 Success - 2025-12-07 01:01:57
cramjam 2.11.0 Failed
  error: subprocess-exited-with-error
  
  × Preparing metadata (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [10 lines of output]
      Checking for Rust toolchain....
      Running `maturin pep517 write-dist-info --metadata-directory /tmp/pip-modern-metadata-oo9iylsb --interpreter /tmp/tmpvlvehhay/venv/bin/python`
      error: failed to parse manifest at `/tmp/pip-install-snafbhi3/cramjam_3a34bc1c0cda4b98aaefe7876d614ee6/Cargo.toml`
      
      Caused by:
        `resolver` setting `3` is not valid, valid options are "1" or "2"
      💥 maturin failed
        Caused by: Cargo metadata failed. Does your crate compile with `cargo build`?
        Caused by: `cargo metadata` exited with an error:
      Error running maturin: Command '['maturin', 'pep517', 'write-dist-info', '--metadata-directory', '/tmp/pip-modern-metadata-oo9iylsb', '--interpreter', '/tmp/tmpvlvehhay/venv/bin/python']' returned non-zero exit status 1.
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
2025-05-20 23:54:56
jupyter-server-terminals 0.5.3 Success - 2025-05-20 19:39:34
ipython-pygments-lexers 1.1.1 Success - 2025-05-20 20:03:35
pycryptodomex 3.23.0 Success - 2025-05-20 17:26:40
fqdn 1.5.1 Success - 2025-05-20 17:53:39
delta-spark 4.0.1 Failed
  error: subprocess-exited-with-error
  
  × installing build dependencies for pyspark did not run successfully.
  │ exit code: 1
  ╰─> [11 lines of output]
      Traceback (most recent call last):
        File "/tmp/tmp9_24byxw/venv/lib/python3.13t/site-packages/pip/__pip-runner__.py", line 50, in <module>
          runpy.run_module("pip", run_name="__main__", alter_sys=True)
          ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "<frozen runpy>", line 226, in run_module
        File "<frozen runpy>", line 98, in _run_module_code
        File "<frozen runpy>", line 88, in _run_code
        File "/tmp/tmp9_24byxw/venv/lib/python3.13t/site-packages/pip/__main__.py", line 8, in <module>
          if sys.path[0] in ("", os.getcwd()):
                                 ~~~~~~~~~^^
      FileNotFoundError: [Errno 2] No such file or directory
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed to build 'pyspark' when installing build dependencies for pyspark
2026-01-11 01:02:08
docker-pycreds 0.4.0 Success - 2025-05-20 20:41:37
pandas-stubs 2.3.3.260113 Success - 2026-01-14 01:02:22
mock 5.2.0 Success - 2025-05-20 19:59:40
isoduration 20.11.0 Success - 2025-05-20 19:35:23
redshift-connector 2.1.10 Failed
ux-x86_64-cpython-313t/lxml/includes
      copying src/lxml/includes/etree_defs.h -> build/lib.linux-x86_64-cpython-313t/lxml/includes
      copying src/lxml/includes/lxml-version.h -> build/lib.linux-x86_64-cpython-313t/lxml/includes
      creating build/lib.linux-x86_64-cpython-313t/lxml/isoschematron/resources/rng
      copying src/lxml/isoschematron/resources/rng/iso-schematron.rng -> build/lib.linux-x86_64-cpython-313t/lxml/isoschematron/resources/rng
      creating build/lib.linux-x86_64-cpython-313t/lxml/isoschematron/resources/xsl
      copying src/lxml/isoschematron/resources/xsl/RNG2Schtrn.xsl -> build/lib.linux-x86_64-cpython-313t/lxml/isoschematron/resources/xsl
      copying src/lxml/isoschematron/resources/xsl/XSD2Schtrn.xsl -> build/lib.linux-x86_64-cpython-313t/lxml/isoschematron/resources/xsl
      creating build/lib.linux-x86_64-cpython-313t/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
      copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/iso_abstract_expand.xsl -> build/lib.linux-x86_64-cpython-313t/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
      copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/iso_dsdl_include.xsl -> build/lib.linux-x86_64-cpython-313t/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
      copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/iso_schematron_message.xsl -> build/lib.linux-x86_64-cpython-313t/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
      copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/iso_schematron_skeleton_for_xslt1.xsl -> build/lib.linux-x86_64-cpython-313t/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
      copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/iso_svrl_for_xslt1.xsl -> build/lib.linux-x86_64-cpython-313t/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
      copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/readme.txt -> build/lib.linux-x86_64-cpython-313t/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
      running build_ext
      building 'lxml.etree' extension
      creating build/temp.linux-x86_64-cpython-313t/src/lxml
      cc -pthread -fno-strict-overflow -Wsign-compare -Wunreachable-code -DNDEBUG -g -O3 -Wall -fPIC -fPIC -DCYTHON_CLINE_IN_TRACEBACK=0 -I/usr/include/libxml2 -Isrc -Isrc/lxml/includes -I/tmp/tmpne8ggyz0/venv/include -I/root/.local/share/uv/python/cpython-3.13.9+freethreaded-linux-x86_64-gnu/include/python3.13t -c src/lxml/etree.c -o build/temp.linux-x86_64-cpython-313t/src/lxml/etree.o -w
      src/lxml/etree.c:7210:80: error: unknown type name ‘__pyx_vectorcallfunc’; did you mean ‘vectorcallfunc’?
       7210 | static CYTHON_INLINE PyObject *__Pyx_PyVectorcall_FastCallDict(PyObject *func, __pyx_vectorcallfunc vc, PyObject *const *args, size_t nargs, PyObject *kw);
            |                                                                                ^~~~~~~~~~~~~~~~~~~~
            |                                                                                vectorcallfunc
      src/lxml/etree.c:299059:69: error: unknown type name ‘__pyx_vectorcallfunc’; did you mean ‘vectorcallfunc’?
      299059 | static PyObject *__Pyx_PyVectorcall_FastCallDict_kw(PyObject *func, __pyx_vectorcallfunc vc, PyObject *const *args, size_t nargs, PyObject *kw)
             |                                                                     ^~~~~~~~~~~~~~~~~~~~
             |                                                                     vectorcallfunc
      src/lxml/etree.c:299104:80: error: unknown type name ‘__pyx_vectorcallfunc’; did you mean ‘vectorcallfunc’?
      299104 | static CYTHON_INLINE PyObject *__Pyx_PyVectorcall_FastCallDict(PyObject *func, __pyx_vectorcallfunc vc, PyObject *const *args, size_t nargs, PyObject *kw)
             |                                                                                ^~~~~~~~~~~~~~~~~~~~
             |                                                                                vectorcallfunc
      src/lxml/etree.c: In function ‘__Pyx_CyFunction_CallAsMethod’:
      src/lxml/etree.c:299793:6: error: unknown type name ‘__pyx_vectorcallfunc’; did you mean ‘vectorcallfunc’?
      299793 |      __pyx_vectorcallfunc vc = __Pyx_CyFunction_func_vectorcall(cyfunc);
             |      ^~~~~~~~~~~~~~~~~~~~
             |      vectorcallfunc
      Compile failed: command '/usr/bin/cc' failed with exit code 1
      creating tmp
      cc -I/usr/include/libxml2 -I/usr/include/libxml2 -c /tmp/xmlXPathInitzpjxdypu.c -o tmp/xmlXPathInitzpjxdypu.o
      cc tmp/xmlXPathInitzpjxdypu.o -lxml2 -o a.out
      error: command '/usr/bin/cc' failed with exit code 1
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for lxml
error: failed-wheel-build-for-install

× Failed to build installable wheels for some pyproject.toml based projects
╰─> lxml
2025-11-19 01:02:03
spacy 3.8.11 Failed
-none-any.whl.metadata (3.3 kB)
      Collecting typing-inspection>=0.4.2 (from pydantic<3.0.0,>=2.0.0->thinc<8.4.0,>=8.3.4)
        Using cached typing_inspection-0.4.2-py3-none-any.whl.metadata (2.6 kB)
      Using cached cython-3.2.1-py3-none-any.whl (1.3 MB)
      Using cached cymem-2.0.13-cp313-cp313t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl (286 kB)
      Using cached murmurhash-1.0.15-cp313-cp313t-manylinux1_x86_64.manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_5_x86_64.whl (164 kB)
      Using cached numpy-2.3.5-cp313-cp313t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl (16.7 MB)
      Downloading catalogue-2.0.10-py3-none-any.whl (17 kB)
      Downloading confection-0.1.5-py3-none-any.whl (35 kB)
      Using cached pydantic-2.12.4-py3-none-any.whl (463 kB)
      Downloading wasabi-1.1.3-py3-none-any.whl (27 kB)
      Using cached setuptools-80.9.0-py3-none-any.whl (1.2 MB)
      Using cached annotated_types-0.7.0-py3-none-any.whl (13 kB)
      Using cached packaging-25.0-py3-none-any.whl (66 kB)
      Using cached typing_extensions-4.15.0-py3-none-any.whl (44 kB)
      Using cached typing_inspection-0.4.2-py3-none-any.whl (14 kB)
      Building wheels for collected packages: preshed, thinc, pydantic-core, srsly
        Building wheel for preshed (pyproject.toml): started
        Building wheel for preshed (pyproject.toml): finished with status 'done'
        Created wheel for preshed: filename=preshed-3.0.12-cp313-cp313t-linux_x86_64.whl size=899003 sha256=055026f0d9d092da4f70d3299609db1e213e2853fdd156fcd7cdc596b137ac82
        Stored in directory: /root/.cache/pip/wheels/f9/72/70/91c13df9d2cca53c98be5c2fdbf4f054a801cf1e6967169246
        Building wheel for thinc (pyproject.toml): started
        Building wheel for thinc (pyproject.toml): still running...
        Building wheel for thinc (pyproject.toml): finished with status 'done'
        Created wheel for thinc: filename=thinc-8.3.10-cp313-cp313t-linux_x86_64.whl size=3852412 sha256=ef0fe576c88ac454cf1f8fa08fb1409fc7b5bc0183582ec71c9fdc4b3ac31961
        Stored in directory: /root/.cache/pip/wheels/95/b5/70/2643286e19f3feebb3df33e57ad52f3e06f960dbb9aa285c2d
        Building wheel for pydantic-core (pyproject.toml): started
        Building wheel for pydantic-core (pyproject.toml): finished with status 'error'
        error: subprocess-exited-with-error
      
        × Building wheel for pydantic-core (pyproject.toml) did not run successfully.
        │ exit code: 1
        ╰─> [14 lines of output]
            Running `maturin pep517 build-wheel -i /tmp/tmpbdcfshtn/venv/bin/python --compatibility off`
            🍹 Building a mixed python/rust project
            🔗 Found pyo3 bindings
            🐍 Found CPython 3.13t at /tmp/tmpbdcfshtn/venv/bin/python
            📡 Using build options bindings from pyproject.toml
            warning: unused manifest key: lints
            error: package `tinystr v0.7.6` cannot be built because it requires rustc 1.67 or newer, while the currently active rustc version is 1.63.0
            Either upgrade to rustc 1.67 or newer, or use
            cargo update -p tinystr@0.7.6 --precise ver
            where `ver` is the latest version of `tinystr` supporting rustc 1.63.0
            💥 maturin failed
              Caused by: Failed to build a native library through cargo
              Caused by: Cargo build finished with "exit status: 101": `env -u CARGO PYO3_BUILD_EXTENSION_MODULE="1" PYO3_ENVIRONMENT_SIGNATURE="cpython-3.13-64bit" PYO3_PYTHON="/tmp/tmpbdcfshtn/venv/bin/python" PYTHON_SYS_EXECUTABLE="/tmp/tmpbdcfshtn/venv/bin/python" "cargo" "rustc" "--profile" "release" "--message-format" "json-render-diagnostics" "--manifest-path" "/tmp/pip-install-l403gy6_/pydantic-core_3e396060b82846138f08ad4ce7922131/Cargo.toml" "--lib"`
            Error: command ['maturin', 'pep517', 'build-wheel', '-i', '/tmp/tmpbdcfshtn/venv/bin/python', '--compatibility', 'off'] returned non-zero exit status 1
            [end of output]
      
        note: This error originates from a subprocess, and is likely not a problem with pip.
        ERROR: Failed building wheel for pydantic-core
        Building wheel for srsly (pyproject.toml): started
        Building wheel for srsly (pyproject.toml): finished with status 'done'
        Created wheel for srsly: filename=srsly-2.5.2-cp313-cp313t-linux_x86_64.whl size=1235208 sha256=fbc344694536d08883845b3e162a377ea5dfdea6e2c1786f34d7f203dfc4b292
        Stored in directory: /root/.cache/pip/wheels/8c/75/19/f59d500c6315d254fbeed1773e5ab96c275885916ac72fbf97
      Successfully built preshed thinc srsly
      Failed to build pydantic-core
      error: failed-wheel-build-for-install
      
      × Failed to build installable wheels for some pyproject.toml based projects
      ╰─> pydantic-core
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed to build 'spacy' when installing build dependencies for spacy
2025-11-18 01:22:46
pydata-google-auth 1.9.1 Success - 2025-05-20 18:58:51
gremlinpython 3.8.0 Success - 2025-11-18 01:23:21
terminado 0.18.1 Success - 2025-05-20 17:53:52
twine 6.2.0 Failed
  error: subprocess-exited-with-error
  
  × pip subprocess to install build dependencies did not run successfully.
  │ exit code: 1
  ╰─> [43 lines of output]
      Collecting maturin<2,>=1.8.6
        Downloading maturin-1.9.4-py3-none-manylinux_2_12_x86_64.manylinux2010_x86_64.musllinux_1_1_x86_64.whl.metadata (16 kB)
      Collecting cffi>=1.14
        Downloading cffi-2.0.0.tar.gz (523 kB)
        Installing build dependencies: started
        Installing build dependencies: finished with status 'done'
        Getting requirements to build wheel: started
        Getting requirements to build wheel: finished with status 'error'
        error: subprocess-exited-with-error
      
        × Getting requirements to build wheel did not run successfully.
        │ exit code: 1
        ╰─> [20 lines of output]
            Traceback (most recent call last):
              File "/tmp/tmpnt0nvqrn/venv/lib/python3.13t/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 389, in <module>
                main()
                ~~~~^^
              File "/tmp/tmpnt0nvqrn/venv/lib/python3.13t/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 373, in main
                json_out["return_val"] = hook(**hook_input["kwargs"])
                                         ~~~~^^^^^^^^^^^^^^^^^^^^^^^^
              File "/tmp/tmpnt0nvqrn/venv/lib/python3.13t/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 143, in get_requires_for_build_wheel
                return hook(config_settings)
              File "/tmp/pip-build-env-w3cvep8w/overlay/lib/python3.13t/site-packages/setuptools/build_meta.py", line 331, in get_requires_for_build_wheel
                return self._get_build_requires(config_settings, requirements=[])
                       ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
              File "/tmp/pip-build-env-w3cvep8w/overlay/lib/python3.13t/site-packages/setuptools/build_meta.py", line 301, in _get_build_requires
                self.run_setup()
                ~~~~~~~~~~~~~~^^
              File "/tmp/pip-build-env-w3cvep8w/overlay/lib/python3.13t/site-packages/setuptools/build_meta.py", line 317, in run_setup
                exec(code, locals())
                ~~~~^^^^^^^^^^^^^^^^
              File "<string>", line 22, in <module>
            RuntimeError: CFFI does not support the free-threaded build of CPython 3.13. Upgrade to free-threaded 3.14 or newer to use CFFI with the free-threaded build.
            [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.
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× pip subprocess to install build dependencies 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.
2025-05-20 20:19:42

Python 3.14t Compatibility Results

Library Version Build Result Error Details Last Updated At
pytest-asyncio 1.3.0 Success - 2025-11-11 01:30:03
python-utils 3.9.1 Success - 2025-05-20 17:47:50
html5lib 1.1 Success - 2025-05-20 19:01:05
selenium 4.39.0 Success - 2025-12-07 01:02:21
cramjam 2.11.0 Success - 2025-05-21 01:39:35
jupyter-server-terminals 0.5.3 Success - 2025-05-20 22:32:23
ipython-pygments-lexers 1.1.1 Success - 2025-05-20 23:51:33
pycryptodomex 3.23.0 Success - 2025-05-20 15:48:39
fqdn 1.5.1 Success - 2025-05-20 17:46:47
delta-spark 4.0.1 Failed
  error: subprocess-exited-with-error
  
  × installing build dependencies for pyspark did not run successfully.
  │ exit code: 1
  ╰─> [11 lines of output]
      Traceback (most recent call last):
        File "/tmp/tmpdu6zok73/venv/lib/python3.14t/site-packages/pip/__pip-runner__.py", line 50, in <module>
          runpy.run_module("pip", run_name="__main__", alter_sys=True)
          ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "<frozen runpy>", line 226, in run_module
        File "<frozen runpy>", line 98, in _run_module_code
        File "<frozen runpy>", line 88, in _run_code
        File "/tmp/tmpdu6zok73/venv/lib/python3.14t/site-packages/pip/__main__.py", line 8, in <module>
          if sys.path[0] in ("", os.getcwd()):
                                 ~~~~~~~~~^^
      FileNotFoundError: [Errno 2] No such file or directory
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed to build 'pyspark' when installing build dependencies for pyspark
2026-01-11 01:02:12
docker-pycreds 0.4.0 Success - 2025-05-20 20:22:40
pandas-stubs 2.3.3.260113 Success - 2026-01-14 01:02:37
mock 5.2.0 Success - 2025-05-20 17:48:05
isoduration 20.11.0 Success - 2025-05-20 21:43:48
redshift-connector 2.1.10 Failed
ux-x86_64-cpython-314t/lxml/includes
      copying src/lxml/includes/etree_defs.h -> build/lib.linux-x86_64-cpython-314t/lxml/includes
      copying src/lxml/includes/lxml-version.h -> build/lib.linux-x86_64-cpython-314t/lxml/includes
      creating build/lib.linux-x86_64-cpython-314t/lxml/isoschematron/resources/rng
      copying src/lxml/isoschematron/resources/rng/iso-schematron.rng -> build/lib.linux-x86_64-cpython-314t/lxml/isoschematron/resources/rng
      creating build/lib.linux-x86_64-cpython-314t/lxml/isoschematron/resources/xsl
      copying src/lxml/isoschematron/resources/xsl/RNG2Schtrn.xsl -> build/lib.linux-x86_64-cpython-314t/lxml/isoschematron/resources/xsl
      copying src/lxml/isoschematron/resources/xsl/XSD2Schtrn.xsl -> build/lib.linux-x86_64-cpython-314t/lxml/isoschematron/resources/xsl
      creating build/lib.linux-x86_64-cpython-314t/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
      copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/iso_abstract_expand.xsl -> build/lib.linux-x86_64-cpython-314t/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
      copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/iso_dsdl_include.xsl -> build/lib.linux-x86_64-cpython-314t/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
      copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/iso_schematron_message.xsl -> build/lib.linux-x86_64-cpython-314t/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
      copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/iso_schematron_skeleton_for_xslt1.xsl -> build/lib.linux-x86_64-cpython-314t/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
      copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/iso_svrl_for_xslt1.xsl -> build/lib.linux-x86_64-cpython-314t/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
      copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/readme.txt -> build/lib.linux-x86_64-cpython-314t/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
      running build_ext
      building 'lxml.etree' extension
      creating build/temp.linux-x86_64-cpython-314t/src/lxml
      cc -pthread -fno-strict-overflow -Wsign-compare -Wunreachable-code -DNDEBUG -g -O3 -Wall -fPIC -fPIC -DCYTHON_CLINE_IN_TRACEBACK=0 -I/usr/include/libxml2 -Isrc -Isrc/lxml/includes -I/tmp/tmpzgoge9p1/venv/include -I/root/.local/share/uv/python/cpython-3.14.0+freethreaded-linux-x86_64-gnu/include/python3.14t -c src/lxml/etree.c -o build/temp.linux-x86_64-cpython-314t/src/lxml/etree.o -w
      src/lxml/etree.c:7210:80: error: unknown type name ‘__pyx_vectorcallfunc’; did you mean ‘vectorcallfunc’?
       7210 | static CYTHON_INLINE PyObject *__Pyx_PyVectorcall_FastCallDict(PyObject *func, __pyx_vectorcallfunc vc, PyObject *const *args, size_t nargs, PyObject *kw);
            |                                                                                ^~~~~~~~~~~~~~~~~~~~
            |                                                                                vectorcallfunc
      src/lxml/etree.c:299059:69: error: unknown type name ‘__pyx_vectorcallfunc’; did you mean ‘vectorcallfunc’?
      299059 | static PyObject *__Pyx_PyVectorcall_FastCallDict_kw(PyObject *func, __pyx_vectorcallfunc vc, PyObject *const *args, size_t nargs, PyObject *kw)
             |                                                                     ^~~~~~~~~~~~~~~~~~~~
             |                                                                     vectorcallfunc
      src/lxml/etree.c:299104:80: error: unknown type name ‘__pyx_vectorcallfunc’; did you mean ‘vectorcallfunc’?
      299104 | static CYTHON_INLINE PyObject *__Pyx_PyVectorcall_FastCallDict(PyObject *func, __pyx_vectorcallfunc vc, PyObject *const *args, size_t nargs, PyObject *kw)
             |                                                                                ^~~~~~~~~~~~~~~~~~~~
             |                                                                                vectorcallfunc
      src/lxml/etree.c: In function ‘__Pyx_CyFunction_CallAsMethod’:
      src/lxml/etree.c:299793:6: error: unknown type name ‘__pyx_vectorcallfunc’; did you mean ‘vectorcallfunc’?
      299793 |      __pyx_vectorcallfunc vc = __Pyx_CyFunction_func_vectorcall(cyfunc);
             |      ^~~~~~~~~~~~~~~~~~~~
             |      vectorcallfunc
      Compile failed: command '/usr/bin/cc' failed with exit code 1
      creating tmp
      cc -I/usr/include/libxml2 -I/usr/include/libxml2 -c /tmp/xmlXPathInit6g_4dgty.c -o tmp/xmlXPathInit6g_4dgty.o
      cc tmp/xmlXPathInit6g_4dgty.o -lxml2 -o a.out
      error: command '/usr/bin/cc' failed with exit code 1
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for lxml
error: failed-wheel-build-for-install

× Failed to build installable wheels for some pyproject.toml based projects
╰─> lxml
2025-11-19 01:02:25
spacy 3.8.11 Success - 2025-11-18 02:29:01
pydata-google-auth 1.9.1 Success - 2025-05-20 23:12:02
gremlinpython 3.8.0 Success - 2025-11-18 02:29:07
terminado 0.18.1 Success - 2025-05-20 18:48:38
twine 6.2.0 Failed
  error: subprocess-exited-with-error
  
  × Preparing metadata (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [10 lines of output]
      Checking for Rust toolchain....
      Running `maturin pep517 write-dist-info --metadata-directory /tmp/pip-modern-metadata-6_j7nvqx --interpreter /tmp/tmpl6qpn703/venv/bin/python`
      error: failed to parse lock file at: /tmp/pip-install-lbv2amiw/nh3_50aa200729da483aaa5c106ef90a204a/Cargo.lock
      
      Caused by:
        lock file version `4` was found, but this version of Cargo does not understand this lock file, perhaps Cargo needs to be updated?
      💥 maturin failed
        Caused by: Cargo metadata failed. Does your crate compile with `cargo build`?
        Caused by: `cargo metadata` exited with an error:
      Error running maturin: Command '['maturin', 'pep517', 'write-dist-info', '--metadata-directory', '/tmp/pip-modern-metadata-6_j7nvqx', '--interpreter', '/tmp/tmpl6qpn703/venv/bin/python']' returned non-zero exit status 1.
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
2025-05-20 20:16:54