Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.xs4all.nl!newsfeed3.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.024 X-Spam-Evidence: '*H*': 0.95; '*S*': 0.00; 'subject:Python': 0.06; 'string': 0.09; 'enhancements': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'semantic': 0.09; 'strings.': 0.09; 'subject:Why': 0.09; 'backwards': 0.16; 'clockwork': 0.16; 'considers': 0.16; 'finney': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'tuples,': 0.16; 'elements': 0.16; 'fix': 0.17; 'packages.': 0.19; 'header:User-Agent:1': 0.23; 'subject:like': 0.24; 'versions': 0.24; '(or': 0.24; 'posts': 0.26; 'header:X-Complaints-To:1': 0.27; 'point': 0.28; "i'm": 0.30; 'comments': 0.31; 'agreed.': 0.31; 'breaking': 0.31; 'minor': 0.31; 'releases,': 0.31; 'writes:': 0.31; 'another': 0.32; 'agree': 0.35; 'version': 0.36; 'next': 0.36; 'useful': 0.36; 'url:org': 0.36; 'should': 0.36; 'throughout': 0.37; 'sometimes': 0.38; 'ben': 0.38; 'convention': 0.38; 'to:addr :python-list': 0.38; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'everybody': 0.60; 'numbers': 0.61; 'simply': 0.61; 'skip:\xe2 10': 0.65; 'series': 0.66; '8bit%:21': 0.69; 'expectations': 0.74; 'glad': 0.83; '"simply': 0.84; '3.10': 0.84; 'confusion.': 0.84; 'received:125': 0.84; 'several)': 0.84; 'termed': 0.84; 'edwards': 0.91; 'hong': 0.91; 'kong': 0.91 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Ben Finney Subject: Re: Why Python 4.0 won't be like Python 3.0 Date: Tue, 19 Aug 2014 08:27:48 +1000 References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Gmane-NNTP-Posting-Host: jigong.madmonks.org X-Public-Key-ID: 0xAC128405 X-Public-Key-Fingerprint: 517C F14B B2F3 98B0 CB35 4855 B8B2 4C06 AC12 8405 X-Public-Key-URL: http://www.benfinney.id.au/contact/bfinney-pubkey.asc X-Post-From: Ben Finney User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:KTRAr4wJ3ghwMjV1w23AKNhTlzA= X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 30 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1408400880 news.xs4all.nl 2911 [2001:888:2000:d::a6]:40362 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:76521 Grant Edwards writes: > 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. This consensus is sometimes termed “semantic versioning”, that is, giving semantic meaning to the structural elements of a version string . I'm glad someone has taken the time to codify that sensible and useful de-facto standard for version strings. > I don't think one (or several) blog posts is going to change the > perceptions and expectations that have been coditioned into us by > decades of experience with x.0 versions of countless software > packages. If it's just another in a a series of incremental "bug fix > and minor enhancements without breaking backwards incompatibility" > releases, you simply do not call it vers x.0. Agreed. The convention is well established and rogues deviate from it at the peril of unnecessary confusion. -- \ “Guaranteed to work throughout its useful life.” —packaging for | `\ clockwork toy, Hong Kong | _o__) | Ben Finney