Why Python won't work on .net

[Cameron Laird]

In article <m3isksttf8.fsf at mira.informatik.hu-berlin.de>,
Martin v. Löwis <martin at v.loewis.de> wrote:
			.
			.
			.
>As for generating MSIL byte codes: This is also possible, and has been
>demonstrated. It also has been demonstrated that an initial
>implementation is likely to be *very* slow.
>
>The question is whether a Python implementation for .NET would be CLS
>compliant (CLS == Common Language Specification). The existing
>implementation has shown that this is not possible without giving up
>parts of the Python semantics.
			.
			.
			.
>No. Instead, most .NET users will find out that .NET is *not* a
>juggernaut, but restricted to C#, in practice. So Python might even
>survive .NET :-)
			.
		[still other points
		elided for space]
			.
			.
Martin's right.  Everything he says here is true, AND
it's not what the .NET Propaganda Ministry teaches, so
I think it's worth repeating.

.NET (and C#, for that matter) is (are) an interesting
technologic story.  It's certainly not a purely evil
conspiracy to contaminate our body fluids; on the other
hand, it's not the greatest thing since the domestica-
tion of the camel, as sometimes portrayed.  I'm putting
my bet on Python outlasting .NET.
-- 

Cameron Laird <claird at phaseit.net>
Business:  http://www.Phaseit.net