Well, I'd argue that its not about trying to be all things to all
programmers - its about finding the most reasonable way to handle one
of the (relatively few) ways that the meta-models of the CLR and
Python don't match up well.
In a way, this is not unlike the situation with methods. The fact tha
On 3/31/06, Brian Lloyd <[EMAIL PROTECTED]> wrote:
> In C# you can explicitly name a generic type, a la Dictionary<,>. That
> syntax won't work in Python, of course. Looking at IP, it seems to allow
> the apparent Python name to be the unmangled IL name so you can
> naturally use the name.
> The p
My vote is to keep Python pure, i.e. import SomeGeneric_TT or foo =
TwoParamGeneric<<2 are simply un-Pythonic.
It is amusing that the .NET framework has incorporated a feature
--Generics-- that make it more useful, and indeed more like Python, and the
Python community is now trying to emulate a so
