(original) (raw)

On 05/30/2015 07:26 AM, Toshio Kuratomi wrote:

Porting performance features from python 3 to python 2 has the disadvantage of cutting into a compelling business case for users to move forward to python 3.\[1\]� so doing this has a cost to python 3 adoption.� But, the question is whether there is a benefit that outweighs that cost. \[...\]

Backporting performance enhancements from 3 to 2 does seem to be counterproductive from the perspective of the Core Dev community.� But certainly in this case, when Intel drops a major bundle of working code in our collective lap, it absolutely feels like the right thing to me to check it in and support it.� And happily the Python Core Dev community generally does the right thing.

Consider the flip side--what if we'd refused to accept it?� What sort of signal would that be to the Python community?� I don't know, but I'd guess that people would harbor ill will and distrust.� I'd rather the community liked and trusted us; that makes it more likely they'll listen when we say "honest, Python 3 is better than 2--c'mon over!"

/arry

p.s. Supporting this patch also helps cut into PyPy's reported performance lead--that is, if they ever upgrade speed.pypy.org from comparing against Python \*2.7.2\*.