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
contourpy 1.3.3 Success - 2025-05-20 15:31:53
transformers 4.57.1 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-2spq72lb --interpreter /tmp/tmpt4_3cm6k/venv/bin/python`
      error: failed to parse lock file at: /tmp/pip-install-vagdvuk3/tokenizers_324e81e91e804f6bbd9163381a218859/bindings/python/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-2spq72lb', '--interpreter', '/tmp/tmpt4_3cm6k/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 16:37:37
crashtest 0.4.1 Success - 2025-05-20 15:33:06
mako 1.3.10 Success - 2025-05-20 15:58:53
parso 0.8.5 Success - 2025-05-20 16:37:52
langchain-core 0.3.79 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-k0dn7a6z --interpreter /tmp/tmpr0knrsfq/venv/bin/python`
      error: failed to parse lock file at: /tmp/pip-install-_7hz9pms/orjson_f35dc21b3d92468aad5a3d181264838c/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-k0dn7a6z', '--interpreter', '/tmp/tmpr0knrsfq/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 16:57:51
py 1.11.0 Success - 2025-05-20 16:57:22
cython 3.1.4 Success - 2025-05-20 15:32:11
cleo 2.1.0 Success - 2025-05-20 15:58:59
zstandard 0.25.0 Success - 2025-05-20 15:31:46
typing-inspect 0.9.0 Success - 2025-05-20 15:59:09
ruamel-yaml-clib 0.2.14 Failed
             ^~~~~~~~~~~
            |                                                                                          |
            |                                                                                          char *
      yaml.h:636:43: note: expected ‘yaml_char_t *’ {aka ‘unsigned char *’} but argument is of type ‘char *’
        636 |         yaml_char_t *anchor, yaml_char_t *tag, int implicit,
            |                              ~~~~~~~~~~~~~^~~
      _ruamel_yaml.c: At top level:
      _ruamel_yaml.c:31652:69: error: unknown type name ‘__pyx_vectorcallfunc’; did you mean ‘vectorcallfunc’?
      31652 | static PyObject *__Pyx_PyVectorcall_FastCallDict_kw(PyObject *func, __pyx_vectorcallfunc vc, PyObject *const *args, size_t nargs, PyObject *kw)
            |                                                                     ^~~~~~~~~~~~~~~~~~~~
            |                                                                     vectorcallfunc
      _ruamel_yaml.c:31697:80: error: unknown type name ‘__pyx_vectorcallfunc’; did you mean ‘vectorcallfunc’?
      31697 | static CYTHON_INLINE PyObject *__Pyx_PyVectorcall_FastCallDict(PyObject *func, __pyx_vectorcallfunc vc, PyObject *const *args, size_t nargs, PyObject *kw)
            |                                                                                ^~~~~~~~~~~~~~~~~~~~
            |                                                                                vectorcallfunc
      _ruamel_yaml.c: In function ‘__Pyx_CyFunction_CallAsMethod’:
      _ruamel_yaml.c:32386:6: error: unknown type name ‘__pyx_vectorcallfunc’; did you mean ‘vectorcallfunc’?
      32386 |      __pyx_vectorcallfunc vc = __Pyx_CyFunction_func_vectorcall(cyfunc);
            |      ^~~~~~~~~~~~~~~~~~~~
            |      vectorcallfunc
      _ruamel_yaml.c:2252:45: warning: initialization of ‘int’ from ‘vectorcallfunc’ {aka ‘struct _object * (*)(struct _object *, struct _object * const*, long unsigned int,  struct _object *)’} makes integer from pointer without a cast [-Wint-conversion]
       2252 | #define __Pyx_CyFunction_func_vectorcall(f) (((PyCFunctionObject*)f)->vectorcall)
            |                                             ^
      _ruamel_yaml.c:32386:32: note: in expansion of macro ‘__Pyx_CyFunction_func_vectorcall’
      32386 |      __pyx_vectorcallfunc vc = __Pyx_CyFunction_func_vectorcall(cyfunc);
            |                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      _ruamel_yaml.c:32389:16: warning: implicit declaration of function ‘__Pyx_PyVectorcall_FastCallDict’; did you mean ‘__Pyx_PyObject_FastCallDict’? [-Wimplicit-function-declaration]
      32389 |         return __Pyx_PyVectorcall_FastCallDict(func, vc, &PyTuple_GET_ITEM(args, 0), (size_t)PyTuple_GET_SIZE(args), kw);
            |                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
            |                __Pyx_PyObject_FastCallDict
      _ruamel_yaml.c:32389:16: warning: returning ‘int’ from a function with return type ‘PyObject *’ {aka ‘struct _object *’} makes pointer from integer without a cast [-Wint-conversion]
      32389 |         return __Pyx_PyVectorcall_FastCallDict(func, vc, &PyTuple_GET_ITEM(args, 0), (size_t)PyTuple_GET_SIZE(args), kw);
            |                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      exiting tmpfile {'full_package_name': 'ruamel.yaml.clib', 'version_info': (0, 2, 14), '__version__': '0.2.14', 'version_timestamp': '2025-09-22 18:47:49', 'author': 'Anthon van der Neut', 'author_email': 'a.van.der.neut@ruamel.eu', 'description': 'C version of reader, parser and emitter for ruamel.yaml derived from libyaml', 'license': 'MIT', 'entry_points': None, 'nested': True, 'binary_only': True, 'since': 2019, 'ext_modules': [{'name': '_ruamel_yaml', 'src': ['_ruamel_yaml.c', 'api.c', 'writer.c', 'dumper.c', 'loader.c', 'reader.c', 'scanner.c', 'parser.c', 'emitter.c'], 'lib': [], 'test': '\n            int main(int argc, char* argv[])\n            {\n              /* prevent warning */\n              return 0;\n            }\n            '}], 'classifiers': ['Programming Language :: Python :: Implementation :: CPython', 'Topic :: Software Development :: Libraries :: Python Modules'], 'keywords': 'yaml 1.2 parser c-library config', 'wheels': {'windows': 'appveyor', 'linux': 'libyaml-devel', 'macos': 'builder@macos'}, 'url_doc': 'https://yaml.dev/doc/{full_package_name}/', 'supported': [(3, 9)], 'python_requires': '>=3.9', 'tox': {'env': '*'}, 'manifest': 'include README.md LICENSE setup.py *.c *.h *.pxd *.pyx'}
      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 ruamel-yaml-clib
error: failed-wheel-build-for-install

× Failed to build installable wheels for some pyproject.toml based projects
╰─> ruamel-yaml-clib
2025-05-20 16:38:10
mypy 1.18.2 Success - 2025-05-20 16:58:03
installer 0.7.0 Success - 2025-05-20 16:37:50
tornado 6.5.2 Success - 2025-05-20 15:32:50
stack-data 0.6.3 Success - 2025-05-20 16:58:22
opentelemetry-exporter-otlp-proto-http 1.37.0 Success - 2025-05-20 15:32:07
ruff 0.14.0 Success - 2025-05-20 15:59:16
python-json-logger 4.0.0 Success - 2025-05-20 15:59:23
torch 2.9.0 Success - 2025-05-20 17:02:42

Python 3.14t Compatibility Results

Library Version Build Result Error Details Last Updated At
contourpy 1.3.3 Success - 2025-05-20 16:52:24
transformers 4.57.1 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-a6miyjpb --interpreter /tmp/tmp1a9d382h/venv/bin/python`
      error: failed to parse lock file at: /tmp/pip-install-7_c95__e/tokenizers_604e8c9f70234285a69c91b90cd16c4e/bindings/python/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-a6miyjpb', '--interpreter', '/tmp/tmp1a9d382h/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 16:44:10
crashtest 0.4.1 Success - 2025-05-20 16:45:15
mako 1.3.10 Success - 2025-05-20 16:45:21
parso 0.8.5 Success - 2025-05-20 16:44:21
langchain-core 0.3.79 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-cx_diecq --interpreter /tmp/tmphq2nq4l5/venv/bin/python`
      error: failed to parse lock file at: /tmp/pip-install-xuoq773j/orjson_0bffb6a2e478428392cdc724160ef93b/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-cx_diecq', '--interpreter', '/tmp/tmphq2nq4l5/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 15:45:01
py 1.11.0 Success - 2025-05-20 15:44:36
cython 3.1.4 Success - 2025-05-20 15:44:10
cleo 2.1.0 Success - 2025-05-20 18:17:02
zstandard 0.25.0 Success - 2025-05-20 15:43:54
typing-inspect 0.9.0 Success - 2025-05-20 18:17:12
ruamel-yaml-clib 0.2.14 Failed
             ^~~~~~~~~~~
            |                                                                                          |
            |                                                                                          char *
      yaml.h:636:43: note: expected ‘yaml_char_t *’ {aka ‘unsigned char *’} but argument is of type ‘char *’
        636 |         yaml_char_t *anchor, yaml_char_t *tag, int implicit,
            |                              ~~~~~~~~~~~~~^~~
      _ruamel_yaml.c: At top level:
      _ruamel_yaml.c:31652:69: error: unknown type name ‘__pyx_vectorcallfunc’; did you mean ‘vectorcallfunc’?
      31652 | static PyObject *__Pyx_PyVectorcall_FastCallDict_kw(PyObject *func, __pyx_vectorcallfunc vc, PyObject *const *args, size_t nargs, PyObject *kw)
            |                                                                     ^~~~~~~~~~~~~~~~~~~~
            |                                                                     vectorcallfunc
      _ruamel_yaml.c:31697:80: error: unknown type name ‘__pyx_vectorcallfunc’; did you mean ‘vectorcallfunc’?
      31697 | static CYTHON_INLINE PyObject *__Pyx_PyVectorcall_FastCallDict(PyObject *func, __pyx_vectorcallfunc vc, PyObject *const *args, size_t nargs, PyObject *kw)
            |                                                                                ^~~~~~~~~~~~~~~~~~~~
            |                                                                                vectorcallfunc
      _ruamel_yaml.c: In function ‘__Pyx_CyFunction_CallAsMethod’:
      _ruamel_yaml.c:32386:6: error: unknown type name ‘__pyx_vectorcallfunc’; did you mean ‘vectorcallfunc’?
      32386 |      __pyx_vectorcallfunc vc = __Pyx_CyFunction_func_vectorcall(cyfunc);
            |      ^~~~~~~~~~~~~~~~~~~~
            |      vectorcallfunc
      _ruamel_yaml.c:2252:45: warning: initialization of ‘int’ from ‘vectorcallfunc’ {aka ‘struct _object * (*)(struct _object *, struct _object * const*, long unsigned int,  struct _object *)’} makes integer from pointer without a cast [-Wint-conversion]
       2252 | #define __Pyx_CyFunction_func_vectorcall(f) (((PyCFunctionObject*)f)->vectorcall)
            |                                             ^
      _ruamel_yaml.c:32386:32: note: in expansion of macro ‘__Pyx_CyFunction_func_vectorcall’
      32386 |      __pyx_vectorcallfunc vc = __Pyx_CyFunction_func_vectorcall(cyfunc);
            |                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      _ruamel_yaml.c:32389:16: warning: implicit declaration of function ‘__Pyx_PyVectorcall_FastCallDict’; did you mean ‘__Pyx_PyObject_FastCallDict’? [-Wimplicit-function-declaration]
      32389 |         return __Pyx_PyVectorcall_FastCallDict(func, vc, &PyTuple_GET_ITEM(args, 0), (size_t)PyTuple_GET_SIZE(args), kw);
            |                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
            |                __Pyx_PyObject_FastCallDict
      _ruamel_yaml.c:32389:16: warning: returning ‘int’ from a function with return type ‘PyObject *’ {aka ‘struct _object *’} makes pointer from integer without a cast [-Wint-conversion]
      32389 |         return __Pyx_PyVectorcall_FastCallDict(func, vc, &PyTuple_GET_ITEM(args, 0), (size_t)PyTuple_GET_SIZE(args), kw);
            |                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      exiting tmpfile {'full_package_name': 'ruamel.yaml.clib', 'version_info': (0, 2, 14), '__version__': '0.2.14', 'version_timestamp': '2025-09-22 18:47:49', 'author': 'Anthon van der Neut', 'author_email': 'a.van.der.neut@ruamel.eu', 'description': 'C version of reader, parser and emitter for ruamel.yaml derived from libyaml', 'license': 'MIT', 'entry_points': None, 'nested': True, 'binary_only': True, 'since': 2019, 'ext_modules': [{'name': '_ruamel_yaml', 'src': ['_ruamel_yaml.c', 'api.c', 'writer.c', 'dumper.c', 'loader.c', 'reader.c', 'scanner.c', 'parser.c', 'emitter.c'], 'lib': [], 'test': '\n            int main(int argc, char* argv[])\n            {\n              /* prevent warning */\n              return 0;\n            }\n            '}], 'classifiers': ['Programming Language :: Python :: Implementation :: CPython', 'Topic :: Software Development :: Libraries :: Python Modules'], 'keywords': 'yaml 1.2 parser c-library config', 'wheels': {'windows': 'appveyor', 'linux': 'libyaml-devel', 'macos': 'builder@macos'}, 'url_doc': 'https://yaml.dev/doc/{full_package_name}/', 'supported': [(3, 9)], 'python_requires': '>=3.9', 'tox': {'env': '*'}, 'manifest': 'include README.md LICENSE setup.py *.c *.h *.pxd *.pyx'}
      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 ruamel-yaml-clib
error: failed-wheel-build-for-install

× Failed to build installable wheels for some pyproject.toml based projects
╰─> ruamel-yaml-clib
2025-05-20 16:52:41
mypy 1.18.2 Success - 2025-05-20 16:45:32
installer 0.7.0 Success - 2025-05-20 16:52:26
tornado 6.5.2 Success - 2025-05-20 16:45:09
stack-data 0.6.3 Success - 2025-05-20 16:45:38
opentelemetry-exporter-otlp-proto-http 1.37.0 Success - 2025-05-20 16:44:27
ruff 0.14.0 Success - 2025-05-20 15:45:27
python-json-logger 4.0.0 Success - 2025-05-20 15:46:18
torch 2.9.0 Failed
ERROR: Could not find a version that satisfies the requirement torch==2.8.0 (from versions: none)
ERROR: No matching distribution found for torch==2.8.0
2025-05-20 18:17:19