Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #76568

Re: Why Python 4.0 won't be like Python 3.0

Show all headers | View raw

On 2014-08-19, Steven D'Aprano <steve+comp.lang.python@pearwood.info> wrote:
> Grant Edwards wrote:
>
>> On 2014-08-18, Ethan Furman <ethan@stoneleaf.us> wrote:
>>> On 08/18/2014 07:51 AM, Grant Edwards wrote:
>>>>
>>>> To all of us out here in user-land a change in the first value in the
>>>> version tuple means breakage and incompatibilities. And when the
>>>> second value is "0", you avoid it until some other sucker has found
>>>> the bugs and a few more minor releases have come out.
>>>
>>> Even our own 3.0 was like that.
>> 
>> So was 2.0, only it wasn't quite as distruptive as 3.0.
>
> How was it disruptive? It was as backward compatible to 1.5 as any point
> release can be expected to be. There were syntax changes, but they added
> new syntax, and didn't take anything away.
>
> In my opinion, 2.6 was a bigger change than 2.0 from the perspective of
> backwards compatibility. 2.6 finally made raising from strings an error.

I'm probably conflating the 1.5.2/2.0 and the 2.6 stuff.  I do
remember delaying moving from 1.5.2 -> 2.0 until I really had to, but 
I don't remember why.

-- 
Grant Edwards               grant.b.edwards        Yow! Oh, I get it!!
                                  at               "The BEACH goes on", huh,
                              gmail.com            SONNY??

Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Why Python 4.0 won't be like Python 3.0 Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-08-17 13:37 +0100
  Re: Why Python 4.0 won't be like Python 3.0 Grant Edwards <invalid@invalid.invalid> - 2014-08-18 14:51 +0000
    Re: Why Python 4.0 won't be like Python 3.0 Chris Angelico <rosuav@gmail.com> - 2014-08-19 01:03 +1000
    Re: Why Python 4.0 won't be like Python 3.0 "ElChino" <elchino@cnn.cn> - 2014-08-18 19:00 +0200
      Re: Why Python 4.0 won't be like Python 3.0 Ethan Furman <ethan@stoneleaf.us> - 2014-08-18 10:15 -0700
      Re: Why Python 4.0 won't be like Python 3.0 Chris Angelico <rosuav@gmail.com> - 2014-08-19 09:46 +1000
    Re: Why Python 4.0 won't be like Python 3.0 Ethan Furman <ethan@stoneleaf.us> - 2014-08-18 10:14 -0700
      Re: Why Python 4.0 won't be like Python 3.0 Grant Edwards <invalid@invalid.invalid> - 2014-08-18 21:09 +0000
        Re: Why Python 4.0 won't be like Python 3.0 Emile van Sebille <emile@fenx.com> - 2014-08-18 14:45 -0700
        Re: Why Python 4.0 won't be like Python 3.0 Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-08-19 10:25 +1000
          Re: Why Python 4.0 won't be like Python 3.0 Grant Edwards <invalid@invalid.invalid> - 2014-08-19 14:27 +0000
            Re: Why Python 4.0 won't be like Python 3.0 Skip Montanaro <skip@pobox.com> - 2014-08-19 09:37 -0500
              Re: Why Python 4.0 won't be like Python 3.0 Grant Edwards <invalid@invalid.invalid> - 2014-08-19 14:51 +0000
              Re: Why Python 4.0 won't be like Python 3.0 Johann Hibschman <jhibschman@gmail.com> - 2014-08-19 10:56 -0400
            Re: Why Python 4.0 won't be like Python 3.0 Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-08-20 03:44 +1000
    Re: Why Python 4.0 won't be like Python 3.0 Ben Finney <ben+python@benfinney.id.au> - 2014-08-19 08:27 +1000
      Re: Why Python 4.0 won't be like Python 3.0 Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-08-19 11:00 +1000
    Re: Why Python 4.0 won't be like Python 3.0 Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-08-19 10:05 +1000
      Re: Why Python 4.0 won't be like Python 3.0 Chris Angelico <rosuav@gmail.com> - 2014-08-19 10:30 +1000
    Re: Why Python 4.0 won't be like Python 3.0 Tim Delaney <timothy.c.delaney@gmail.com> - 2014-08-19 10:47 +1000
  Re: Why Python 4.0 won't be like Python 3.0 wxjmfauth@gmail.com - 2014-08-19 12:04 -0700

csiph-web