This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rhettinger
Recipients benjamin.peterson, rhettinger, vstinner
Date 2017-01-07.19:43:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1483818189.55.0.465235431837.issue29188@psf.upfronthosting.co.za>
In-reply-to
Content
> I would prefer to use the "same code" (or almost) on all maintained
> versions of Python: 2.7, 3.5, 3.6 and 3.7. It should ease the
> maintenance for bugfixes and enhancements.

This is VERY far from our historical policy for backports.  Python 2.7 is supposed to be getting more stable over time (that is one of its chief virtues).  We don't want to risk the kind of mini-catastrophe that got published in 3.6 (issue29085).  

If you want to push for this, there needs to be a thorough discussion on python-dev (there are tons of possible backports that could be made if the rationale was "I would prefer to use the same code on all maintained versions").
History
Date User Action Args
2017-01-07 19:43:09rhettingersetrecipients: + rhettinger, vstinner, benjamin.peterson
2017-01-07 19:43:09rhettingersetmessageid: <1483818189.55.0.465235431837.issue29188@psf.upfronthosting.co.za>
2017-01-07 19:43:09rhettingerlinkissue29188 messages
2017-01-07 19:43:09rhettingercreate