Vladimir,
Your examples seem to indicate that you've misunderstood the change
that's proposed for Python 3000. Especially this:
On 5/17/06, Vladimir 'Yu' Stepanov [EMAIL PROTECTED] wrote:
# BEGIN: Emulation python3000
if type(a) is not type(b) and (
Guido van Rossum wrote:
On 5/11/06, Vladimir 'Yu' Stepanov [EMAIL PROTECTED] wrote:
If for Python-3000 similar it will be shown concerning types
str(), int(), complex() and so on, and the type of exceptions
will strongly vary, it will make problematic redefinition of
behavior of function of
On 5/11/06, Vladimir 'Yu' Stepanov [EMAIL PROTECTED] wrote:
If for Python-3000 similar it will be shown concerning types
str(), int(), complex() and so on, and the type of exceptions
will strongly vary, it will make problematic redefinition of
behavior of function of sorting.
I don't see what
Guido van Rossum wrote:
On 5/6/06, Vladimir Yu. Stepanov [EMAIL PROTECTED] wrote:
[proposing a total ordering between types]
It Ain't Gonna Happen. (From now on, I'll write this as IAGH.)
In Python 3000, we'll actually *remove* ordering between arbitrary
types as a feature; only types that
On 5/11/06, Vladimir 'Yu' Stepanov [EMAIL PROTECTED] wrote:
If for Python-3000 similar it will be shown concerning types
str(), int(), complex() and so on, and the type of exceptions
will strongly vary, it will make problematic redefinition of
behavior of function of sorting.
Not really.
Guido van Rossum wrote:
On 5/11/06, Vladimir 'Yu' Stepanov [EMAIL PROTECTED] wrote:
If for Python-3000 similar it will be shown concerning types
str(), int(), complex() and so on, and the type of exceptions
will strongly vary, it will make problematic redefinition of
behavior of function of
Edward Loper wrote:
It might be useful in some cases to have a keyword argument to
sort/sorted that says to ignore exceptions arising from comparing
elements, and leaves the ordering of non-comparable values undefined.
Why? Far better to use a key (or cmp if you really want) that imposes a
of a sequence.
It is sad. I did not know it. Therefore and have not understood.
I have looked in Google on python dev total ordering. On intentions to
correct this problem I have not found anything. It already earlier was
discussed ?
Not really. It has to do with how non-comparable
On 5/6/06, Vladimir Yu. Stepanov [EMAIL PROTECTED] wrote:
[proposing a total ordering between types]
It Ain't Gonna Happen. (From now on, I'll write this as IAGH.)
In Python 3000, we'll actually *remove* ordering between arbitrary
types as a feature; only types that explicitly care to be ordered
