Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #20891
| From | Ben Finney <ben+python@benfinney.id.au> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: [RELEASED] Release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3 |
| References | <mailman.160.1330192578.3037.python-list@python.org> <87ty2ern8j.fsf@benfinney.id.au> <mailman.169.1330247038.3037.python-list@python.org> |
| Date | 2012-02-26 23:21 +1100 |
| Message-ID | <87haydss3w.fsf@benfinney.id.au> (permalink) |
| Organization | Unlimited download news at news.astraweb.com |
Chris Angelico <rosuav@gmail.com> writes: > On Sun, Feb 26, 2012 at 7:51 PM, Ben Finney <ben+python@benfinney.id.au> wrote: > > If you're pleased to announce their immediate availability, then > > please do that! > > Isn't it perfectly accurate to say that the RCs are now available? Yes. What's not reasonable is to say that a candidate for release – i.e. something *prior to* release, by definition – is nevertheless released. > Considering that "Release candidates" immediately followed "RELEASED" > in the subject line, I don't see any confusion. Unless “release candidate” means nothing like what those words imply, it can't be both a release candidate *and* released. Either it's released, or it's not. If it's a release candidate, it's not released yet. If it's released, it's no longer a candidate for release. Saying it's simultaneously both is the confusion. -- \ “The Things to do are: the things that need doing, that you see | `\ need to be done, and that no one else seems to see need to be | _o__) done.” —Richard Buckminster Fuller, 1970-02-16 | Ben Finney
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[RELEASED] Release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3 Benjamin Peterson <benjamin@python.org> - 2012-02-25 12:56 -0500
Re: [RELEASED] Release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3 Ben Finney <ben+python@benfinney.id.au> - 2012-02-26 19:51 +1100
Re: [RELEASED] Release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3 Chris Angelico <rosuav@gmail.com> - 2012-02-26 20:03 +1100
Re: [RELEASED] Release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3 Ben Finney <ben+python@benfinney.id.au> - 2012-02-26 23:21 +1100
Re: [RELEASED] Release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3 Chris Angelico <rosuav@gmail.com> - 2012-02-27 00:01 +1100
Re: [RELEASED] Release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3 Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-02-26 13:08 +0000
Re: [RELEASED] Release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3 Jean-Michel Pichavant <jeanmichel@sequans.com> - 2012-02-27 15:23 +0100
Re: [RELEASED] Release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3 Terry Reedy <tjreedy@udel.edu> - 2012-02-26 17:20 -0500
Re: [RELEASED] Release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3 Benjamin Peterson <benjamin@python.org> - 2012-02-27 14:16 +0000
Re: [RELEASED] Release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3 Ben Finney <ben+python@benfinney.id.au> - 2012-02-28 08:30 +1100
csiph-web