> Right, because the whole point of Python is as a glue language for native libraries. I have had this precise need before. I have a multi-threaded native libr

> Right, because the whole point of Python is as a glue language for native libraries. I have had this precise need before. I have a multi-threaded native library. The multi-threading is essential for reasonable performance in the intended use-case for the library. But my users can't write C++ to call it; they'd like Python. They'd like to extend certain specific operations that my native library does during processing. I give them Python bindings. The perf gained by running the library on multiple cores is completely negated whenever multiple C++ threads of my native library need to run Python code.