Slashdot Mirror

← Back to Stories (view on slashdot.org)

IronPython Moving Forward Again

Posted by timothy on from the interesting-times dept.

immytay writes " Jim Hugunin (Jython, Numeric, and other projects) has issued the first release of IronPython since joining Microsoft in August of last year. IronPython runs on .NET and Mono and is supposedly faster than the C version of Python. This new version is 0.7, while 0.6 was released last summer and covered here. According to the IronPython mailing list, Jim has help from a Microsoft co-worker, and he plans to work toward IronPython 1.0."

3 of 61 comments (clear)

  1. Re:Except for Mono by nightski · · Score: 5, Informative

    What you will find is that this is a bunch of BS. They took advantage of the new features in the .NET Framework 2.0 - which will be standardized in the CLI. .NET 2.0 isn't even out by Microsoft yet - so of course Mono isn't going to support it. But Mono is planning on eventually having full support for .NET 2.0. So it will work. Wait till 1.0 - everything will be working then.

    --
    "Ideas without action are worthless."
  2. Re:Phrase it any way you like by chris_mahan · · Score: 3, Informative

    Someobody expand on that: I believe ironPython is not compatible with .Net 1.0 because of python itself, something to do with dynamic allocation in python. It's something that is supposed to work in 2.0

    --

    "Piter, too, is dead."

  3. Re:Phrase it any way you like by IainCartwright · · Score: 3, Informative

    Paolo Molaro (one of the mono guys) said on the Ironpython mailing list:

    "IronPython 0.7 compiles with the current mono from svn (not with the released 1.1.5, though the patch is minimal)."

    And Jim Hugunin has said in the same place that if Ironpython does not compile because it deviates from the spec. then it is a bug and should be entered as such.

    Try and avoid knee jerk reactions. You'll just annoy your high horse.