Should non-security 2.7 bugs be fixed?

[Mark Lawrence]

On 20/07/2015 03:16, Rustom Mody wrote:
> On Monday, July 20, 2015 at 7:16:50 AM UTC+5:30, Mark Lawrence wrote:
>> On 20/07/2015 02:20, Devin Jeanpierre wrote:
>>
>>>
>>> I don't like how this is being redirected to "surely you
>>> misunderstood" or "I don't believe you". The fact that some core devs
>>> are hostile to 2.x development is really bleedingly obvious, you
>>> shouldn't need quotes or context thrown at you. The rhetoric almost
>>> always shies _just_ short of ceasing bugfixes (until 2020, when that
>>> abruptly becomes a cracking good idea). e.g. in "2.7 is here until
>>> 2020, please don't call it a waste".
>>>
>>
>> A couple of things.
>>
>> First "some core devs are hostile", actually some have stated that
>> they're simply not interested in 2.7 and will not work on it.
>>
>> Second how has the thread got here, as it was originally asking about
>> back porting bug fixes from 3.x to 2.7?  Further it said:-
>>
>> <quote>
>> If the vast majority of Python programmers are focused on 2.7, why are
>> volunteers to help fix 2.7 bugs so scarce?
>> </quote>
>>
>> So I most humbly suggest, as I may have hinted at once or twice earlier
>> in this thread, that people either put up or shut up.
>
> I just ran the following command
> $ hg log --template "{author|person}\n" | sort | uniq -c | sort -nr
>
> as giving all the committers to python in sorted order.
> I get the list below.
> Dont see any Mark Lawrence there
> Of course I dont know hg at all well... Just picked up the above command from
> http://stackoverflow.com/questions/6126678/how-to-list-commiters-sorted-by-number-of-commits-commit-count
>
> So... May I humbly ask where are your precious commits??
>

Thank you for showing your complete ignorance as to how Python works.

-- 
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.

Mark Lawrence