From the release page:
We have just released IronPython 0.9.2. In addition to focusing on the CPython regression test suite
and fixing bugs, we also spent time prepairing IronPython for PDC 2005 conference where Jim spent the
whole of the last week. There were many changes in IronPython codebase, mostly inspired by getting
the regression tests running and adding CPython 2.4 features.
Given their focus and the bugs they’ve been fixing, it looks like they are getting ever closer to an environment which is (mostly) compatible with CPython.
It also looks like running IronPython under mono on a non-MS OS is becoming less painful. I was actually able to run the IronPythonConsole (which is just an IronPython interpreter shell) under mono 184.108.40.206 on Linux (Ubuntu Hoary specifically). This isn’t a huge deal, but I was further able to compile a simple C# module with mono 220.127.116.11, import it using IronPython 0.9.2, instantiate an object from it, and then call a method on the object. I have had some issues with only certain versions of IronPython being able to do that with certain versions of mono. I’m hopeful that what we’re seeing is progress.
If/when IronPython becomes 100% CPython compatible and 100% mono runnable, would you use it? Why or why not?