[Python-Dev] Backward-incompatible change to random.randrange in 2.7.6

Nick Coghlan ncoghlan at gmail.com
Wed Dec 18 11:51:56 CET 2013

On 18 December 2013 20:17, Chris Angelico <rosuav at gmail.com> wrote:
> On Wed, Dec 18, 2013 at 8:43 PM, Serhiy Storchaka <storchaka at gmail.com> wrote:
>> 18.12.13 04:40, Benjamin Peterson написав(ла):
>>> Mostly yes, but at least you could tell people to upgrade straight to
>>> 2.7.7 and skip 2.7.6.
>> It'll make the people to postpone the upgrade to 2.7.6 (which fixes many
>> security bugs) until 2.7.7 release,  instead of correcting their
>> morally-broken programs.
> If this is considered enough breakage to be a problem, would it be
> possible to issue a or 2.7.6+fixed release that's identical to
> 2.7.6 but with this change reverted? It'd be a minor mess, but then
> people would still get those security fixes, and it means not breaking
> stuff in a point release.

If we revert it, it means we do 2.7.7 ASAP so that *everyone* can just
skip straight to 2.7.7.

That kind of user visible change shouldn't have been made in a point
release, regardless of what the docs said. It just isn't worth the
risk of breaking the code of people that are relying on what's
possible rather than what the docs say.


Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

More information about the Python-Dev mailing list