This would reduce the complexity of uuid.UUID and also if the way it compares changes, one would't have to change all the compare methods.
Attached is a patch.

Can you provide test cases for this code?

Yes, will do so.

@Brian Curtin
It appears that there are tests for UUID ordering. [0]
I will run the tests.

[0] http://hg.python.org/cpython/file/d1e6a48dfb0d/Lib/test/test_uuid.py#l188

Damn, I forgot to add import functools.
Here is a fixed version that passes test_uuid.

Oh darn, I included another bugs changes in it.
I unlinked the v2 patch and have attached issue17001-v2.patch

Except for mistakenly included functional.rst changes, the patch looks good for me.

I recommend against this patch.  The code generated by functools.total_ordering is less efficient than the existing code and it doesn't handle the NotImplemented logic very well.

total_ordering() is a shortcut, not a best practice.

Performance info using the attached program:
~2.5 sec, original
~3.5 sec, patched
(patched version is 40% slower)
Is anybody doing the comparison in performance-critical cases?

On 21 January 2013 02:42, Raymond Hettinger <report@bugs.python.org> wrote:

> NotImplemented

Can you please elaborate on "it doesn't handle the NotImplemented logic
very well".
AFAIK both will give NotImplemented for the same values.

@Raymond Hettinger
Why? Please respond to my comments.