Microsoft IronPython?

[Luis M. González]

Ray wrote:
> But then again, once you start using .NET class you're tied to .NET
> anyway so this is not a big problem, I think--although the more
> perfectionist among us might like to isolate parts of Python code that
> are .NET/IP specific to make porting easier if it ever comes to that...

That's exactly what they did with version 1.0.
For example, if you wanted to turn a string into uppercase, in previous
versions you could have done:

'hello'.upper() or 'hello'.ToUpper()

That means, the python way and the .NET way.
But now if you want to do it the .NET way, you have to add the
statement "import clr" before.
So I guess you can isolate your coding to standard python if you want
or go forward and use all the CLR capabilities.