Re: Should non-security 2.7 bugs be fixed?

From	Mark Lawrence <breamoreboy@yahoo.co.uk>
Subject	Re: Should non-security 2.7 bugs be fixed?
Date	2015-07-19 14:52 +0100
References	<moenuj$f11$1@ger.gmane.org> <moeqtn$mh0$1@ger.gmane.org> <mailman.693.1437269689.3674.python-list@python.org> <87egk4zu6m.fsf@jester.gateway.sonic.net>
Newsgroups	comp.lang.python
Message-ID	<mailman.714.1437313947.3674.python-list@python.org> (permalink)

Show all headers | View raw

On 19/07/2015 04:45, Paul Rubin wrote:
> Terry Reedy <tjreedy@udel.edu> writes:
>> I am suggesting that if there are 10x as many 2.7only programmers as
>> 3.xonly programmers, and none of the 2.7 programmers is willing to do
>> the backport *of an already accepted patch*, then maybe it should not
>> be done at all.
>
> The patch acceptance/approval process is frankly daunting.
>

Correct, which is why "PEP 0462 -- Core development workflow automation 
for CPython" https://www.python.org/dev/peps/pep-0462/, "PEP 0474 -- 
Creating forge.python.org" https://www.python.org/dev/peps/pep-0474/ and 
a separate core-workflow mailing list exist.

Admittedly things had stalled but I understand that they're being picked 
up again.

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

Mark Lawrence

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: Should non-security 2.7 bugs be fixed? Terry Reedy <tjreedy@udel.edu> - 2015-07-18 21:34 -0400
  Re: Should non-security 2.7 bugs be fixed? Paul Rubin <no.email@nospam.invalid> - 2015-07-18 20:45 -0700
    Re: Should non-security 2.7 bugs be fixed? Rustom Mody <rustompmody@gmail.com> - 2015-07-18 21:04 -0700
    Re: Should non-security 2.7 bugs be fixed? Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-07-19 14:52 +0100

csiph-web