IronPython Moving Forward Again

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."

Comments

Re:Except for Mono

[nightski]

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.

Re:Phrase it any way you like

[chris_mahan]

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

Re:Phrase it any way you like

[IainCartwright]

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.

Common Public License version 1.0

[captwheeler]

from www.ironpython.com

IronPython-0.6 is now available as Open Source Software under the Common Public License version 1.0. A single zip file containing both the source code and the binary executables can be downloaded below.

Re:Vs Psyco?

[lupus-slash]

Mono runs IronPython just fine on linux/ppc, OSX, amd64 etc.

Re:open source maybe, where's the community?

[mike_sucks]

Have a read of this message. If some of these issues have been cleared up, then great!

If Hugunin has issues accepting patches because of who he works for, then that's a shame. I'm glad he thinks that that may change post 1.0, but why will these issues suddently be easier to work around just because the code has reached a stable version? If they can be worked around, why not do so now?

How long will it take for 1.0 to be released? Are people prepared to wait that long rather than forking, starting from scratch or getting behind an alternative effort right away? Will anyone still be around by then to be to be turned into an instant community? These things can't just get turned on or off.

If you'll still (lessend or not) need to get a Passort account and use gotdotnet to be part of the community, that will still be very off putting for many potential hackers. Having a Passport account is an identity theft waiting to happen. Why is required to be a part of the community? A web forum is a massively inefficient way of communicating when compared to a mailing list, why should people have to suffer it?

I still would want some answers to these (and Edd Dumbill's, Miguel de Icaza's and Paolo Molaro's) questions before getting behing IronPython. The fact that such questions are raised at all is troubling, however.