4 ms·
To my knowledge IronPython cannot easily call python extensions written in C/C++. So going with IronPython means using Microsoft's .NET libraries (or the mono c
by fauigerzigerk 18y ago
To my knowledge IronPython cannot easily call python extensions written in C/C++. So going with IronPython means using Microsoft's .NET libraries (or the mono clones) for many tasks, just as using JVM based languages means falling back to Java libraries as a replacement for those Python/Ruby libraries that haven't been reimplemented on top of the VM.
Python has a huge number of libraries and it keeps growing. I don't think the attempt to reimplement everything on top of .NET/Java is going to succeed. The people who maintain these libraries are not going to do it so where's the army of people who will take on such an incredibly boring task? I hope, one day, C/C++ libraries will be conveniently accessible from the VMs.
The only viable alternative would be to implement all Python libraries exclusively in Python. That's something that current maintainers of C/C++ extensions might consider doing. But Python would have to be much faster for this to work.