Source: cvc5 Severity: normal X-Debbugs-Cc: celel...@gmail.com Hello, There are two Python API to CVC5. The base API that closely match the C++ one, and the pythonic API.
The base API is part of the main repository and should be built automatically with the rest of the code. I guess it could be packaged as a separate python3-cvc5 package with very little effort. The pythonic API is another repository and uses the base API. https://github.com/cvc5/cvc5_pythonic_api I don't think packaging the base API would be too much additional work, since it's from the same source code that produces the packages cvc5, libcvc5-dev, libcvc5-1 and libcvc5parser1. Having the pythonic API would be even better, but not necessary. Best regards, Celelibi -- System Information: Debian Release: 12.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-security'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'unstable'), (500, 'stable'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
