Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #94475 > unrolled thread
| Started by | Rick Johnson <rantingrickjohnson@gmail.com> |
|---|---|
| First post | 2015-07-23 15:49 -0700 |
| Last post | 2015-07-23 15:49 -0700 |
| 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? Rick Johnson <rantingrickjohnson@gmail.com> - 2015-07-23 15:49 -0700
| From | Rick Johnson <rantingrickjohnson@gmail.com> |
|---|---|
| Date | 2015-07-23 15:49 -0700 |
| Subject | Re: Should non-security 2.7 bugs be fixed? |
| Message-ID | <69ec07d2-eae9-409c-b54a-ba0fccd47015@googlegroups.com> |
On Wednesday, July 22, 2015 at 11:26:50 PM UTC-5, Jason Swails wrote: > I know my experiences don't hold true for everybody, but I > also don't think they are uncommon (I know several > colleagues that share many aspects of them). And for me, > the *better* Python 2.7 becomes, and the longer it's kept > around, the easier (and more fun!) it makes my transition > to Python 3. So for me at least, arguments like "don't > make Python 2.7 too good or people won't switch" are not > only wrong, but in actuality counter-productive. Thanks for sharing your story. You offer a compelling argument for maintaining Py2.x in peak condition for many years.
Back to top | Article view | comp.lang.python
csiph-web