This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rhettinger
Recipients amaury.forgeotdarc, benjamin.peterson, brett.cannon, christian.heimes, georg.brandl, lemburg, mark.dickinson, pitrou, rhettinger
Date 2008-12-09.09:59:17
SpamBayes Score 0.0006524865
Marked as misclassified No
Message-id <1228816758.56.0.395743984917.issue1717@psf.upfronthosting.co.za>
In-reply-to
Content
Moving cmp() somewhere other than builtins is not progress.  IMO, it
needs to die off and the concept of it needs to disappear completely. 
Code is better without it.  Three-way comparisons are PITA to use --
their only virtue is as an optimization in the few cases where one
three-way test is cheaper to compute than two two-way tests.

The goal for 3.0 was to have one way to do it and thereby simplify the
language.  Tucking it away in a module or writing a new decorator
defeats the purpose.  It simply should die and go away.
History
Date User Action Args
2008-12-09 09:59:18rhettingersetrecipients: + rhettinger, lemburg, brett.cannon, georg.brandl, amaury.forgeotdarc, mark.dickinson, pitrou, christian.heimes, benjamin.peterson
2008-12-09 09:59:18rhettingersetmessageid: <1228816758.56.0.395743984917.issue1717@psf.upfronthosting.co.za>
2008-12-09 09:59:18rhettingerlinkissue1717 messages
2008-12-09 09:59:17rhettingercreate