26 Jan
2006
26 Jan
'06
10:27 a.m.
I must say that Python.NET feels like an approach I would use more than IronPython.
I am second to this opinion. If I do not want\need to embed Python within CLR or .NET application I definitely do not want to install and use an other Python interpreter. CPython interpreter works fine.
There's also the fact that IronPython is too young and requires .NET 2.0. For people who already have a mature application, use 1.1, and/or is already in production IMHO Python.NET is the way to go. -H.