IronPython vs. Python .NET -
I want to use some .NET assemblies written in c # from Python code.
A small research has shown that I have two options:
- Built-in with .NET interface capability / support
- with package Python
What are trade-offs between the two solutions?
If you want to primarily assign your code to the basis on the .NET framework, Recommend IronPathon vs. Python.net IronPython is very native .NET - so it only works great when integrates with other .NET langauges.
If you want to integrate only one or two components from .NET into a standard python application, then Python.NET is good.
There are significant differences when using IronPython - but most of them are quite subtle. The Python.NET standard uses the CPython runtime, so there is a relevant discussion about the difference between the two implementations. The biggest difference in cost of exceptions is that some standard python libraries do not even perform in IronPath because of their implementation.
Comments
Post a Comment