[Python-Dev] PEP 594: update 1
steve at holdenweb.com
Thu May 23 15:25:13 EDT 2019
Besides which, it would be lovely to have a major release that didn't
involve any pain at all for the majority of users!
Our erstwhile BDFL always eschewed two-digit version identifiers- due to
the possibility for confusion about collating sequence, I beleive.. We
should honour his preferences by going from 3.9 to 4.0.
On Thu, May 23, 2019 at 5:49 PM Anders Munch <ajm at flonidan.dk> wrote:
> Fra: Paul Moore [mailto:p.f.moore at gmail.com]:
> > > A major version change serves as a heads up that something is going on
> and you need to check the consequences before upgrading.
> > Python's backward compatibility policy allows breaking changes between
> versions X.Y and X.Y+1 (with a suitable deprecation period). This proposal
> is no different.
> Except perhaps in scale. The same people that upgrade from 3.x to 3.x+1
> without giving it a second thought, just to be on the latest version, will
> hesitate to go from 3.x to 4.y, because the major version change is a hint
> that they should be more careful. That means they're ready for it when
> they get the ModuleNotFoundError exception, instead of feeling ambushed.
> OK, it may be that this is not enough to warrant a 4.0 release, but I do
> think python-dev should get over its fear of major versions sometime. And
> that transitioning to a leaner standard library with some things moved to
> PyPI would not be a bad program statement for a Python 4.0.
> regards, Anders
> Python-Dev mailing list
> Python-Dev at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev