When comparing different types, CPython 2 applies some different rules:
None is sorted first.- Numbers come before other types, and are compared numerically among themselves.
- Other types are ordered by their type name, unless they explicitly implement comparison methods.
In addition, some types implement custom sorting rules and can refuse all attempts to sort. Complex numbers raise an exception when you try to order them, for example, and datetime objects do so when you try to order them relative to other types.
This isn't documented in the Python reference documentation; see the default comparison code in object.c instead. It is an implementation detail and not something your code should ever rely on. The comparison operators documentation states:
Most other objects of built-in types compare unequal unless they are the same object; the choice whether one object is considered smaller or larger than another one is made arbitrarily but consistently within one execution of a program.
The goal was to make comparisons between different types stable when sorting a sequence of mixed objects.
In Python 3, comparison rules have been tightened up; you can only compare objects that explicitly implement comparisons. After years of experience the conclusion was drawn that allowing for arbitrary comparisons was only leading to more confusion; comparing strings with digits in them with integers always confuses newcomers, for example.
Your code would raise an exception instead.
