Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #94077 > unrolled thread
| Started by | Chris Angelico <rosuav@gmail.com> |
|---|---|
| First post | 2015-07-19 10:27 +1000 |
| Last post | 2015-07-19 10:27 +1000 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Should non-security 2.7 bugs be fixed? Chris Angelico <rosuav@gmail.com> - 2015-07-19 10:27 +1000
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2015-07-19 10:27 +1000 |
| Subject | Re: Should non-security 2.7 bugs be fixed? |
| Message-ID | <mailman.692.1437265678.3674.python-list@python.org> |
On Sun, Jul 19, 2015 at 9:36 AM, Terry Reedy <tjreedy@udel.edu> wrote: > 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? I use Linux on all my computers, but I wouldn't be volunteering to help fix kernel bugs, because I'm not competent to. I also compile C code now and then, but don't offer to fix GCC bugs. There may well be huge numbers of people who write Python code who don't feel they can contribute in that way (whether or not that's strictly true - after all, half of Python is written in Python anyway). ChrisA
Back to top | Article view | comp.lang.python
csiph-web