Is it possible to embed PyPy into a .NET application?

PyPy's CLI backend is not as mature as C backend and also does not integrate as well with . NET libraries. While normal PyPy compiled to C is production ready, I wouldn't call the .

NET version production ready. It's also missing the JIT (although some work has been done in this area) and microthreads. Unless someone steps in, IronPython seems to be the only viable option as of now.

PyPy's CLI backend is not as mature as C backend and also does not integrate as well with . NET libraries. While normal PyPy compiled to C is production ready, I wouldn't call the .

NET version production ready. It's also missing the JIT (although some work has been done in this area) and microthreads. Unless someone steps in, IronPython seems to be the only viable option as of now.

Cheers, fijal.

No, there's not. CPython had the ability to access . NET libraries using the now defunct Python for .

NET (see pythonnet.sourceforge.net/), but aside from IronPython there's never been a way to actually embed a Python interpreter into a . NET application. This was one of its main selling points.

On a related note, IronPython (by default) has a smaller stack size than CPython when it comes to recursion. That is, you must pass a "-X:FullFrames" command-line option to ipy. Exe to enable CPython-esque stack frames.

Know this isn't as good as PyPy...but it might help:).

Python Dot Net is not completely dead. Latest files at: sourceforge. Net/projects/pythonnet/files and subversion stats: sourceforge.Net/project/stats/… – markm Jul 27 at 3:31.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.