[snip...]
> Firstly, although you are correct that .NET supports a managed variant of
> C++ (that runs 'on .NET') and it is the same set of tools that you also use
> to compile native code (unmanaged C/C++) this has nothing to do with .NET.
> Python for Windows is compiled with the Visual C++ compiler but it doesn't
> run on .NET. .NET doesn't even use the MSVCRT that compiled native code
> links against - something that causes Ironclad 'difficulties' when managed
> and native code need to share file handles.
>
> Ironclad itself has binary compatibility with Python C extensions, they
> don't need to be recompiled. It uses the .NET FFI (P/Invoke) to work with
> these extensions and on the JVM would use its FFI.
>
> My understanding is that Android now allows native code, so if Dalvik has
> the same FFI APIs and you can compile the Python extensions for it *and*
> Jython runs on Dalvik (not currently the case I believe?) then it could
> work...
>