Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Beyond the syntax of Python, will any of the libraries and built-in functions really work well on .NET? I also don't see how it will be possible for them to really use real .NET as Python has no support for interfaces and real abstract classes from what I've read. It would be one thing to just treat say... XmlNodeList.GetEnumerator()'s return as a Python class, but how does Python for .NET do this: class MyObject(BaseClass, IEnumerator, IComparable): ?
I think it's really cool that Jim's working on a means of using Python on .NET, but I am one of those people who thinks that the Python language as a whole would be better suited with a move to Parrot. It would be a real bitch for both Sun and Microsoft if Parrot not only had PERL6 and Python support, but supported a variant of VisualBasic.NET and Java all of which would be interoperable once compiled to Parrot bytecode.