➜

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 Jim.Jewett
Recipients Jim.Jewett, Lukasa, alex, christian.heimes, dstufft, georg.brandl, giampaolo.rodola, hynek, janssen, larry, python-dev, steve.dower
Date 2016-09-08.16:26:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CA+OGgf5HD4-DU781iCgfN_aMYRETrkw8+yG+Tq16O4KSSLO_=g@mail.gmail.com>
In-reply-to <1473319738.65.0.631343887441.issue27850@psf.upfronthosting.co.za>
Content 
In general,  the rule is that micro versions (such as 3.4.4 to 3.4.5)
should not make any changes that are not clearly bug fixes.  If users would
call the new API (or ABI) differently, it is almost certainly a change that
should be reserved for a development release (3.4 to 3.5).

That said, the two main reasons for exceptions are security  (not an
automatic OK, but at least not an automatic NO) and "no one could possibly
rely on the old behavior", which covers "this wouldn't even compile on this
platform before".
History
Date User Action Args
2016-09-08 16:26:36Jim.Jewettsetrecipients: + Jim.Jewett, georg.brandl, janssen, larry, giampaolo.rodola, christian.heimes, alex, python-dev, hynek, steve.dower, dstufft, Lukasa
2016-09-08 16:26:36Jim.Jewettlinkissue27850 messages
2016-09-08 16:26:35Jim.Jewettcreate