Comments on: Why use IronPython?

By: Michael Foord

Michael Foord — Tue, 11 Nov 2008 16:06:21 +0000

@Jon

F# is interesting – but we’ve already built a product on IronPython. We’re not about to jump ship. :-)

We use threading for both – to keep the GUI thread active whilst spreadsheets are calculating and to allow multiple documents to recalculate concurrently. IronPython is great for concurrency using .NET threads.

By: Jon Harrop

Jon Harrop — Mon, 10 Nov 2008 21:58:12 +0000

You may also like to look at F#. Performance, support, libraries, data structures, algorithms and reliability (without extensive testing) are all much better.

Also, threading is either for concurrency (latency) or for parallelism (throughput). CPython already handles concurrency and if you want parallelism (= performance) you shouldn’t be using any kind of Python anyway.

By: giles

giles — Mon, 10 Nov 2008 14:23:39 +0000

Chris – you’re right, the lack of attributes could be a problem – however, it slipped my mind because it’s not something that’s really impacted us much. The only place I can think of straight away is in our P/Invoke code, where we had to drop down into C#.

I guess serialization is another area where we might have had problems, but we’re using pickle instead.

By: Dew Drop - November 10, 2008 | Alvin Ashcraft's Morning Dew

Dew Drop - November 10, 2008 | Alvin Ashcraft's Morning Dew — Mon, 10 Nov 2008 12:06:23 +0000

[...] Why Use IronPython? (Giles Thomas) [...]

By: Chris Vickerson

Chris Vickerson — Mon, 10 Nov 2008 03:21:30 +0000

what about .Net Attributes? You must have had to interface using System.Attribute… I’ve been playing with IronPython, but this [missing] feature could prevent it from going very far.