Re: python 3's adoption

2010-01-28 Thread mdj
On Jan 29, 12:21 pm, Steven D'Aprano wrote: > "Comes to their senses"? > > There's nothing you can do with __cmp__ that you can't do better with > rich comparisons, and plenty that rich comparisons can do that __cmp__ is > utterly incapable of dealing with. __cmp__ is crippled since it can only >

Re: python 3's adoption

2010-01-28 Thread mdj
On Jan 29, 9:47 am, Paul Boddie wrote: > On 27 Jan, 13:26, Xah Lee wrote: > > > > > So, for practical reasons, i think a “key” parameter is fine. But > > chopping off “cmp” is damaging. When your data structure is complex, > > its order is not embedded in some “key”. Taking out “cmp” makes it > >