[GvR]
> I expect that, given the general trend that different types are not
> comparable, making an exception for None is more likely a source of
> errors than a source of joy.
That is reasonable.
Raymond
___
Python-3000 mailing list
Python-3000@python
On Feb 1, 2008 6:04 PM, Talin <[EMAIL PROTECTED]> wrote:
> I would like to present an argument both for and against the proposal.
>
> Against: I've never personally needed this capability.
>
> For: In many languages, the 'null' value has a special polymorphic
> behavior in that it is considered a s
I would like to present an argument both for and against the proposal.
Against: I've never personally needed this capability.
For: In many languages, the 'null' value has a special polymorphic
behavior in that it is considered a subtype of all reference types. Thus
in C, you can assign NULL to
On Feb 1, 2008 5:18 PM, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
> > You should have been there when this was decided about two years ago.
>
> IIRC, the decision was a general one about cross-type
> comparisons not being turned-on the default. I do not
> recall a specific discussion about None
> You should have been there when this was decided about two years ago.
IIRC, the decision was a general one about cross-type
comparisons not being turned-on the default. I do not
recall a specific discussion about None.
Also, the list at the time was flooded with propositions
ranging from the
You should have been there when this was decided about two years ago.
I really don't want to be tweaking the language spec continuously
between now and the planned release date in ~August.
On Feb 1, 2008 3:56 PM, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
> It was very convenient in Py2.x to ha
It was very convenient in Py2.x to have None comparable to other types and
always rank less than any other type.
I would like to restore that ability.
One example, it helps with heaps to be able to turn an entry into None and have
it sift to the top where the null entries can be popped-off.
R
