Re: [RELEASED] Release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3

2012-02-27 Thread Ben Finney
Benjamin Peterson writes: > Ben Finney benfinney.id.au> writes: > > > > Putting “RELEASED” in the subject, when they're not released and are > > instead *candidates for* release, is confusing and muddies the issue of > > what you even mean by “release”. > > > > {alpha, beta, release candidate,

Re: [RELEASED] Release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3

2012-02-27 Thread Jean-Michel Pichavant
Ben Finney wrote: Chris Angelico writes: On Sun, Feb 26, 2012 at 7:51 PM, Ben Finney 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 reasonab

Re: [RELEASED] Release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3

2012-02-27 Thread Benjamin Peterson
Ben Finney benfinney.id.au> writes: > > Putting “RELEASED” in the subject, when they're not released and are > instead *candidates for* release, is confusing and muddies the issue of > what you even mean by “release”. > {alpha, beta, release candidate, final} \subsetof releases -- http://mai

Re: [RELEASED] Release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3

2012-02-26 Thread Terry Reedy
On 2/26/2012 3:51 AM, Ben Finney wrote: Benjamin Peterson writes: We're pleased to announce the immediate availability of release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3 . If you're pleased to announce their immediate availability, then please do that! Putting “RELEASED” in the

Re: [RELEASED] Release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3

2012-02-26 Thread Steven D'Aprano
On Sun, 26 Feb 2012 23:21:07 +1100, Ben Finney wrote: > Chris Angelico writes: > >> On Sun, Feb 26, 2012 at 7:51 PM, Ben Finney >> 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 a

Re: [RELEASED] Release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3

2012-02-26 Thread Chris Angelico
On Sun, Feb 26, 2012 at 11:21 PM, Ben Finney wrote: > 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

Re: [RELEASED] Release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3

2012-02-26 Thread Ben Finney
Chris Angelico writes: > On Sun, Feb 26, 2012 at 7:51 PM, Ben Finney > 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 f

Re: [RELEASED] Release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3

2012-02-26 Thread Chris Angelico
On Sun, Feb 26, 2012 at 7:51 PM, Ben Finney wrote: > Benjamin Peterson writes: > >> We're pleased to announce the immediate availability of release candidates >> for >> Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3 . > > If you're pleased to announce their immediate availability, then please > do that!

Re: [RELEASED] Release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3

2012-02-26 Thread Ben Finney
Benjamin Peterson writes: > We're pleased to announce the immediate availability of release candidates for > Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3 . If you're pleased to announce their immediate availability, then please do that! Putting “RELEASED” in the subject, when they're not released and

[RELEASED] Release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3

2012-02-25 Thread Benjamin Peterson
We're pleased to announce the immediate availability of release candidates for Python 2.6.8, 2.7.3, 3.1.5, and 3.2.3 . The main impetus for these releases is fixing a security issue in Python's hash based types, dict and set, as described below. Python 2.7.3 and 3.2.3 include the security patch and