[Python-ideas] Should this be considered a bug?

Nick Coghlan ncoghlan at gmail.com
Mon Oct 31 01:20:35 CET 2011


On Mon, Oct 31, 2011 at 9:46 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> I did find an unfortunate case where Python 3 violates this design
> principle - bytes and bytearray objects accept any object that
> implements the buffer interface as the other operand, even in the
> __add__ case.

Interestingly, I found a similar ordering dependency exists for set()
and frozenset():

>>> set() | frozenset()
set()
>>> frozenset() | set()
frozenset()

So the status quo is less consistent than I previously thought.

Regardless, it isn't enough to merely point out that the status quo is
inconsistent. It's necessary to make a case for why the proposed
change is sufficiently better to be worth the cost of making the
change: http://www.boredomandlaziness.org/2011/02/status-quo-wins-stalemate.html

Consider the "it's not worth the hassle" stodgy core developer
response invoked ;)

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia



More information about the Python-ideas mailing list