Make C-API great for FFIs & non-C implementations

[encukou]

In C API strategy draft, there wasn't much opposition to the goal of being “easily usable from non-C languages”. We should seek info on what this should mean from people who make FFIs, bindings and alternate C-API implementations.

Projects to ask:

• [x] nanobind (should include bybind11 & Boost.Python experience) https://github.com/wjakob/nanobind/discussions/31
• [x] PyPy https://mail.python.org/archives/list/pypy-dev@python.org/thread/44IO4GHWBEVIXLFGD4SUNJKFDXOBHILE/
• [x] PyO3 https://github.com/PyO3/pyo3/discussions/2346
• [ ] ctypes.pythonapi python-dev? look thru git history?

From MAL on capi-sig:

• [ ] Boost.Python (C++): https://www.boost.org/
• [ ] SIP (C++): https://www.riverbankcomputing.com/software/sip/
• [ ] Lupa (LUA): https://github.com/scoder/lupa
• [x] Python.NET (.NET): http://pythonnet.github.io/ https://github.com/pythonnet/pythonnet/discussions/1797
• [x] JPype (Java): https://github.com/jpype-project/jpype https://github.com/jpype-project/jpype/discussions/1071
• [ ] Jep (Java): https://github.com/ninia/jep
• [ ] PyJnius (Java): https://github.com/kivy/pyjnius

Not exactly language bindings, but interface to a different programmable eco-system as well:

• [ ] PyXXL (Excel Add-ins): https://www.pyxll.com/ (non-free)
• [ ] PyUNO (OpenOffice/LibreOffice API): http://www.openoffice.org/udk/python/python-bridge.html

And:

• PySide notes