Chris Angelico rosuav at gmail.com
Wed Dec 18 11:17:15 CET 2013

• Previous message: [Python-Dev] Backward-incompatible change to random.randrange in 2.7.6
• Next message: [Python-Dev] Backward-incompatible change to random.randrange in 2.7.6
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

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 2.7.6.1 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.

ChrisA

---

• Previous message: [Python-Dev] Backward-incompatible change to random.randrange in 2.7.6
• Next message: [Python-Dev] Backward-incompatible change to random.randrange in 2.7.6
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list