Should non-security 2.7 bugs be fixed?

[Rick Johnson]

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.