Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #76521
| From | Ben Finney <ben+python@benfinney.id.au> |
|---|---|
| Subject | Re: Why Python 4.0 won't be like Python 3.0 |
| Date | 2014-08-19 08:27 +1000 |
| References | <mailman.13066.1408279206.18130.python-list@python.org> <lst3t9$30d$1@reader1.panix.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.13119.1408400880.18130.python-list@python.org> (permalink) |
Grant Edwards <invalid@invalid.invalid> 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 <URL:http://semver.org/>. 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
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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