Re: [Python.NET] PythonDotNet - IronPyton

2011-01-12 Thread Emmanuel . Lambert
Hello Mark and others, thank you for the clarification. Very interesting, I hadn't though of these two distinct use cases, i.e. : -on the one hand embedding Python scripting in .NET applications -on the other hand calling .NET assemblies from applications that otherwise run outside of the .N

Re: [Python.NET] PythonDotNet - IronPyton

2011-01-10 Thread Oleksii Bidiuk
Hi Emmanuel et al, I wouldn't jump to conclusions that fast. There are situations when you want to use wide variety of C libraries that can be called from CPython but not available directly from IronPython and in the same time trigger application logic written in .NET. An alternative to this is Ir

Re: [Python.NET] PythonDotNet - IronPyton

2011-01-10 Thread Laszlo Sebo
Hi Emmanuel, Python.Net lets you use .net assemblies from within any cpython environment. You can't do that via ironpython. So you can integrate common .net libraries with applications that have their own python interpreters. We use this quite heavily integrating .net with maya, nuke and a l

Re: [Python.NET] PythonDotNet - IronPyton

2011-01-10 Thread Tribble, Brett
2011 9:12 AM To: emmanuel.lamb...@intec.ugent.be Cc: pythondotnet@python.org Subject: Re: [Python.NET] PythonDotNet - IronPyton On Mon, Jan 10, 2011 at 4:18 AM, Emmanuel Lambert wrote: > Hi Oleksii Bidiuk, > > While access to the native Python libraries is apprently a nice feature > o

Re: [Python.NET] PythonDotNet - IronPyton

2011-01-10 Thread Mark Tigges
On Mon, Jan 10, 2011 at 4:18 AM, Emmanuel Lambert wrote: > Hi Oleksii Bidiuk, > > While access to the native Python libraries is apprently a nice feature > of "Python for .NET", I don't think it is very useful in real-world .NET > centric projects (in a corporate environment for example). > An imp

Re: [Python.NET] PythonDotNet - IronPyton

2011-01-10 Thread Emmanuel Lambert
Hi Oleksii Bidiuk, While access to the native Python libraries is apprently a nice feature of "Python for .NET", I don't think it is very useful in real-world .NET centric projects (in a corporate environment for example). An implementation like IronPython restricts itself to the use of native .N

Re: [Python.NET] PythonDotNet - IronPyton

2011-01-10 Thread Oleksii Bidiuk
Hi Emmanuel, The basic differences are highlighted in several discussions like http://stackoverflow.com/questions/1168914/ironpython-vs-python-net In short IronPython is a complete managed implementation of Python interpreter i

[Python.NET] PythonDotNet - IronPyton

2011-01-10 Thread Emmanuel Lambert
Dear all, I was wondering : what is the difference between PythonDotNet and IronPython? It looks like IronPython is rapidly becoming a maturing implementation for the .NET platform, with also a plugin for Visual Studio becoming available : http://ironpython.net/ The distinction between the two im