Ironpython in production environments

My understanding of Iron Python is that it is an implementation of Python which runs under the Microsoft CLR (Common Language Runtime).  The CLR is the foundation for ll of Microsoft's .NET languages, and as such,  I would expect Iron Python would be just as safe in a production environment as any other Microsoft languages.

Typo correction - "all of MIcrosoft's .NET languages".  Without the "a" it looked like I was saying eleven of their languages!

I use IronPython as it is with dependencies on .NET libraries

I plan to port my IronPython  prototype to C#  ( which is relatively straightforward )

I may not have to do this if IronPython can be used in a production environment. I can leave the modify the current IronPython code base and deploy that. Which is why I asked: is this safe to do?

One other point is that, according to that Wikipedia article, Iron Python itself is implemented entirely in C#.... so as far as porting it to C# goes, in a sense, it is already a C# program!

@richard  - I am concerned that the behaviour of my application may not be consistent running in a C# and Python ( jython ) environment. You are probably right that if we test the code extensively under production load it should run as expected.


Does anyone know of any unexpected behaviour from jython applications from a Python or a .NET perspective?