I've used Swig for C++ to Python interop and let me warn you it is a nightmare. The syntax is absurdly terse and convoluted, documentation sucks and good luck trying to search the web for constructs made only of special characters. CLIF is way nicer for C++/Python. If you need other languages then best of luck (Zig, Rust and D are easier than Java and Go at least).
I don't know if it's a feature of Swig, but Swig C++ modules are also hard to use from Python, because they're missing reflection, docstrings, etc. I don't know if it was a shortcoming of the Swig module I was working with (e.g. author didn't bother to add docstrings) or the Swig itself, but it was pretty uncomfortable working with module that provides zero runtime documentation and incomplete documentation.
Also, structure of the resulting module, classes, methods was kind of unpythonic.