IronPython-0.6 For .NET/Mono Debuts

Sunspire writes "IronPython, a Python implementation for the .NET and Mono platforms, has just released its latest version, IronPython-0.6. Touted features include speed, with IronPython being supposedly faster than the native C version of Python, and CLR integration giving full access to the .NET and Mono libraries while still being fully dynamic like regular Python. Is Python, Mono and GTK# the new killer combo for rapid Linux desktop application development?" We previously covered IronPython back in May.

Comments

Re:This is superb

[bdash]

As far as I am aware August 2nd is in the future. Though Jim Hugunin may have been employed by Microsoft while he wrote IronPython, he was working in a group unrelated to .NET and the CLR, and he wrote it in his spare time. I fail to see how this ties Microsoft to his decision to release IronPython as open-source software.

It's the bindings, stupid

[Majix]

One real world problem I see IronPython fixing is the availability (or lack thereof) of up to date bindings for the language. Since IronPython targets the CLR you do not need to write your Python specific bindings for GTK, gnome-libs, etc. anymore. Instead, any Mono language can use the Mono targeting GTK#, gconf#, atk# and so on. This doesn't just affect Python, all smaller languages like Ruby or Haskell, heck even Perl and PHP, could benefit from using a shared set of bindings. Even if they already all have their own versions of GTK, when you want to introduce a new library like gnome-vfs everyone has to go and write their own version of it, which is just wasteful.

Also, Novell throwing their weight behind GTK# gives me confidence that we'll still be receiving updated versions of it a few years from now, which is important when you're trying to sell your PHB on the idea to base your next project on the bindings.

Here's a quick "Hello world" program in IronPython and GTK#, tested with Mono 1.0. It certainly looks slick. Note the neat way of attaching the function callback to the button's clicked signal, when you're coming from the C version of GTK you really appreciate small things like that:

import Gtk

def hello_world (o, args):
print "Hello world!"

Gtk.Application.Init()
window = Gtk.Window ("Hello world!")
button = Gtk.Button ("Hello!")
button.Clicked += hello_world
window.Add (b)
window.ShowAll ()
Gtk.Application.Run ()

Re:It's the bindings, stupid

[clintp]

So slick in fact, I don't even program in Python (much less IronPython) or GTK and think I've found a bug. Shouldn't:

window.Add (b)

be

window.Add ( button)

Otherwise I don't see how the button gets associated with the window.

Re:This is superb

[Anonymous Coward]

Though Jim Hugunin may have been employed by Microsoft while he wrote IronPython . . . he wrote it in his spare time. I fail to see how this ties Microsoft to his decision to release IronPython as open-source software.

Well, it rather depends on whether he was employed by MS at the time. If he was, then his contract almost certainly stipulates that all his code (even what he writes his spare time) are belong to them.