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

References	<mailman.13066.1408279206.18130.python-list@python.org> <lst3t9$30d$1@reader1.panix.com>
Date	2014-08-19 10:47 +1000
Subject	Re: Why Python 4.0 won't be like Python 3.0
From	Tim Delaney <timothy.c.delaney@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.13127.1408409281.18130.python-list@python.org> (permalink)

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On 19 August 2014 00:51, Grant Edwards <invalid@invalid.invalid> wrote:

> On 2014-08-17, Mark Lawrence <breamoreboy@yahoo.co.uk> wrote:
> > A blog from Nick Coghlan
> > http://www.curiousefficiency.org/posts/2014/08/python-4000.html that
> > should help put a few minds to rest.
>
> I agree with the comments that the appellation for "simply the next
> version after 3.9" should be 3.10 and not 4.0.  Everybody I know
> considers SW versions numbers to be dot-separated tuples, not
> floating point numbers.
>
> 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.
>

 No. A major version increase *may* introduce breakage and
incompatibilities. It does not mean that it *has* to introduce breakage and
incompatibilities. If the major version increase is documented as "just
being the next version" then there's no reason to avoid it - unless your
policy is "wait for the first patch release" i.e. never take major.minor.0
but always wait for major.minor.1.

What is more important is that minor and patch version increases should
avoid introducing breakage and incompatibilities wherever possible
(security fixes are one reason to allow incompatibility in a minor release).

BTW I agree with the idea that 4.0 would be an appropriate time to remove
anything that has been deprecated for the requisite number of versions.

Tim Delaney

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