If you haven’t been keeping up with things, IronPython is an implementation of Python for the .Net framework. Basically, you can write Python code, compile it to .Net’s bytecode (I think they call it “Intermediary Language”), and run it from the .Net runtime. Probably more importantly, you can call .Net libraries from Python.
This release has a number of bug fixes, many of which appear to be specifically intended to insure compatibility with “standard” Python. I keep saying it every release, but it warrants saying again. I’m continually pleased that Microsoft is going through as much effort as they are to keep IronPython compatible (in syntax and experience) with standard Python. They could have, at any time, decided to abandon compatibility with Python and to create a press release announcing the creation of a new language, P#. (I know. That doesn’t work with the implied musical connotation of C#.) But they haven’t done so. Oh, wait. That’s right. They’re waiting to hijack the language until after 1.0 final and after they’ve accumulated a sufficiently large user base. I know that thought is running through people’s minds. I confess it’s run through mine at least once. But I don’t think it’s going to happen. At least, I’ll be very surprised if it does.