Path: csiph.com!usenet.pasdenom.info!news.redatomik.org!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.002 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'python,': 0.02; 'pycon': 0.03; 'cpython': 0.05; 'fixes': 0.05; 'cc:addr:python-list': 0.09; 'considered.': 0.09; 'subject:2.7': 0.09; 'vast': 0.09; 'bug': 0.10; 'python': 0.10; 'jan': 0.11; '2.7': 0.13; 'cares': 0.16; 'ecosystem': 0.16; 'reedy': 0.16; 'released.': 0.16; 'subject:non': 0.16; 'thread.': 0.16; 'wrote:': 0.16; 'fixed.': 0.18; 'accepting': 0.18; '2015': 0.20; 'cc:2**0': 0.20; 'cc:addr:python.org': 0.20; 'contributed': 0.20; 'fix': 0.21; 'year,': 0.22; 'fixing': 0.22; 'spring': 0.22; '(or': 0.23; 'sat,': 0.23; 'written': 0.24; 'header:In-Reply-To:1': 0.24; 'developers': 0.26; 'bugs': 0.27; 'question': 0.27; 'message- id:@mail.gmail.com': 0.27; 'about.': 0.29; 'volunteers': 0.29; 'asked': 0.29; 'url:mailman': 0.30; 'code': 0.30; 'initially': 0.30; 'normally': 0.30; 'programmers': 0.30; 'users.': 0.31; 'everyone': 0.31; 'another': 0.32; 'core': 0.32; 'aside': 0.32; 'point': 0.33; 'problem': 0.33; 'url:python': 0.33; 'is?': 0.33; 'surely': 0.33; 'url:listinfo': 0.34; 'gets': 0.35; 'received:google.com': 0.35; 'something': 0.35; 'sometimes': 0.35; 'but': 0.36; 'should': 0.36; 'project': 0.36; 'url:org': 0.36; 'subject:?': 0.36; 'pm,': 0.36; 'subject:: ': 0.37; 'really': 0.37; 'release': 0.37; 'experience,': 0.38; 'summer': 0.38; 'why': 0.39; '2010,': 0.39; 'does': 0.39; 'subject:-': 0.39; 'url:mail': 0.40; 'build': 0.40; 'some': 0.40; 'software': 0.40; 'care': 0.60; 'personally': 0.61; 'making': 0.62; 'ending': 0.63; 'more': 0.63; 'great': 0.63; 'improvements': 0.66; 'reply': 0.68; 'jul': 0.72; 'presented': 0.72; 'lack': 0.76; 'background:': 0.81; '2.7.': 0.84; 'reviewers.': 0.84; 'viewpoints': 0.84; 'officially': 0.91 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=LHxdmKGjTNNPa98+B6cKBk9TLESsuWYkDQaQIaKPAbA=; b=EXSqXjc+f1pJAx7zpYe1zqz2UV2Sn3uaW7dWLxE6tW+GtBohgE0onjFYy4+V8vtskr QaEhvG3LY6F45ktoN+rZHNiqPozIwsKwzgwmiktToVhPzQBjYfiV9sFnjK8kDxKblcg2 i1E0Hwco7fc40HOquRZraQLL1+0PO6LllEcLL/eg23ETyVqSzNbUtRzCFao7zytykbGf PfKM8u8N5FaQTOFx9P5typWGpjONAzZn4MOhX1h4f7Jnle6+F+PIYumHaX6q9Siv/zU6 8JlnXlXrAj2F6byGvp520fhRrkF9U1oXv25Zw5ihL4K6HstBNx3TV4fBGGYwbG4IR6C9 SI0Q== X-Received: by 10.180.104.167 with SMTP id gf7mr8164289wib.86.1437263492140; Sat, 18 Jul 2015 16:51:32 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: Devin Jeanpierre Date: Sat, 18 Jul 2015 16:50:52 -0700 Subject: Re: Should non-security 2.7 bugs be fixed? To: Terry Reedy Cc: "comp.lang.python" Content-Type: text/plain; charset=UTF-8 X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.20+ Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 42 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1437263495 news.xs4all.nl 2839 [2001:888:2000:d::a6]:50923 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:94072 Considering CPython is officially accepting performance improvements to 2.7, surely bug fixes are also allowed? I have contributed both performance improvements and bug fixes to 2.7. In my experience, the problem is not the lack of contributors, it's the lack of code reviewers. I think this is something everyone should care about. The really great thing about working on a project like Python is that not only do you help the programmers who use Python, but also the users who use the software that those programmers create. Python 2.7 is important in the software ecosystem of the world. Fixing bugs and making performance improvements can sometimes significantly help the >1B people who use the software written in Python 2.7. -- Devin On Sat, Jul 18, 2015 at 4:36 PM, Terry Reedy wrote: > I asked the following as an off-topic aside in a reply on another thread. I > got one response which presented a point I had not considered. I would like > more viewpoints from 2.7 users. > > Background: each x.y.0 release normally gets up to 2 years of bugfixes, > until x.(y+1).0 is released. For 2.7, released summer 2010, the bugfix > period was initially extended to 5 years, ending about now. At the spring > pycon last year, the period was extended to 10 years, with an emphasis on > security and build fixed. My general question is what other fixes should be > made? Some specific forms of this question are the following. > > If the vast majority of Python programmers are focused on 2.7, why are > volunteers to help fix 2.7 bugs so scarce? > > Does they all consider it perfect (or sufficient) as is? > > Should the core developers who do not personally use 2.7 stop backporting, > because no one cares if they do? > > -- > Terry Jan Reedy > > -- > https://mail.python.org/mailman/listinfo/python-list