Mailing List Archive: Python: Dev

3.3 release plans

Index | Next | Previous | View Threaded

g.brandl-nospam at gmx

Jun 23, 2012, 3:54 AM

Post #1 of 16 (358 views)
Permalink

3.3 release plans

Hi all,

now that the final PEP scheduled for 3.3 is final, we're entering
the next round of the 3.3 cycle.

I've decided to make Tuesday 26th the big release day. That means:

- Saturday: last feature-level changes that should be done before beta,
e.g. removal of packaging
- Sunday: final feature freeze, bug fixing
- Monday: focus on stability of the buildbots, even unstable ones
- Tuesday: forking of the 3.3.0b1 release clone, tagging, start
of binary building

cheers,
Georg
--
NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone!
Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

g.brandl-nospam at gmx

Jun 23, 2012, 3:22 AM

Post #2 of 16 (343 views)
Permalink

3.3 release plans [In reply to]

Hi all,

I've checked in the (hopefully final) update of PEP 398: all PEP
scale changes are now final or deferred to 3.4.

I also adjusted the release day to be the 26th of June, which leaves
us with the following rough plan:

- Saturday: last large changes, such as removal of packaging
- Sunday: final feature freeze for 3.3; resolve last blockers
from bugs.python.org
- Monday: ensure build stability for stable buildbots, and as
many unstable buildbots as possible
- Tuesday: release clone forked off the main repo; tagging
and start of binary building

cheers,
Georg
--
NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone!
Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

kristjan at ccpgames

Jun 23, 2012, 4:00 AM

Post #3 of 16 (358 views)
Permalink

Re: 3.3 release plans [In reply to]

I realize it is late, but any chance to get http://bugs.python.org/issue15139 in today?

________________________________________
Frá: python-dev-bounces+kristjan=ccpgames.com [at] python [python-dev-bounces+kristjan=ccpgames.com [at] python] fyrir hönd g.brandl-nospam [at] gmx [g.brandl-nospam [at] gmx]
Sent: 23. júní 2012 10:54
To: python-dev [at] python
Efni: [Python-Dev] 3.3 release plans

Hi all,

now that the final PEP scheduled for 3.3 is final, we're entering
the next round of the 3.3 cycle.

I've decided to make Tuesday 26th the big release day. That means:

- Saturday: last feature-level changes that should be done before beta,
e.g. removal of packaging
- Sunday: final feature freeze, bug fixing
- Monday: focus on stability of the buildbots, even unstable ones
- Tuesday: forking of the 3.3.0b1 release clone, tagging, start
of binary building

cheers,
Georg
--
NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone!
Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/kristjan%40ccpgames.com
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

solipsis at pitrou

Jun 23, 2012, 4:12 AM

Post #4 of 16 (355 views)
Permalink

Re: 3.3 release plans [In reply to]

On Sat, 23 Jun 2012 11:00:34 +0000
Kristján Valur Jónsson <kristjan [at] ccpgames> wrote:
> I realize it is late, but any chance to get http://bugs.python.org/issue15139 in today?

-1.

Regards

Antoine.

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

solipsis at pitrou

Jun 23, 2012, 4:54 AM

Post #5 of 16 (354 views)
Permalink

Re: 3.3 release plans [In reply to]

On Sat, 23 Jun 2012 13:12:19 +0200
Antoine Pitrou <solipsis [at] pitrou> wrote:
> On Sat, 23 Jun 2012 11:00:34 +0000
> Kristján Valur Jónsson <kristjan [at] ccpgames> wrote:
> > I realize it is late, but any chance to get http://bugs.python.org/issue15139 in today?
>
> -1.

Let me elaborate: the patch hasn't been reviewed, and it's a very minor
improvement (assuming it's an improvement at all) in a rather delicate
area.

Regards

Antoine.

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

kristjan at ccpgames

Jun 23, 2012, 5:32 AM

Post #6 of 16 (356 views)
Permalink

Re: 3.3 release plans [In reply to]

Au contraire, it is actually a very major improvement, the result of pretty extensive profiling, see http://blog.ccpgames.com/kristjan/2012/05/25/optimizing-python-condition-variables-with-telemetry/

The proposed patch reduces signaling latency in busy applications as demonstrated by the example program from 10s of milliseconds to about one, on my 64 bit windows box. This matters very much for applications using threading.Condition to dispatch work to threads. This includes those using queue.Queue().

K

________________________________________
Frá: python-dev-bounces+kristjan=ccpgames.com [at] python [python-dev-bounces+kristjan=ccpgames.com [at] python] fyrir hönd Antoine Pitrou [solipsis [at] pitrou]
Sent: 23. júní 2012 11:54
To: python-dev [at] python
Efni: Re: [Python-Dev] 3.3 release plans

On Sat, 23 Jun 2012 13:12:19 +0200
Antoine Pitrou <solipsis [at] pitrou> wrote:
> On Sat, 23 Jun 2012 11:00:34 +0000
> Kristján Valur Jónsson <kristjan [at] ccpgames> wrote:
> > I realize it is late, but any chance to get http://bugs.python.org/issue15139 in today?
>
> -1.

Let me elaborate: the patch hasn't been reviewed, and it's a very minor
improvement (assuming it's an improvement at all) in a rather delicate
area.

Regards

Antoine.

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/kristjan%40ccpgames.com
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

solipsis at pitrou

Jun 23, 2012, 5:37 AM

Post #7 of 16 (350 views)
Permalink

Re: 3.3 release plans [In reply to]

On Sat, 23 Jun 2012 12:32:37 +0000
Kristján Valur Jónsson <kristjan [at] ccpgames> wrote:
> Au contraire, it is actually a very major improvement, the result of pretty extensive profiling, see http://blog.ccpgames.com/kristjan/2012/05/25/optimizing-python-condition-variables-with-telemetry/

It might be. But to evaluate it, we have to digest a long technical blog
post, then carefully review the patch (and perhaps even re-do
some measurements). You understand that it's not reasonable to do so
just one day before feature freeze.

Regards

Antoine.
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

lists at cheimes

Jun 23, 2012, 12:55 PM

Post #8 of 16 (338 views)
Permalink

Re: 3.3 release plans [In reply to]

Am 23.06.2012 12:54, schrieb g.brandl-nospam [at] gmx:
> Hi all,
>
> now that the final PEP scheduled for 3.3 is final, we're entering
> the next round of the 3.3 cycle.
>
> I've decided to make Tuesday 26th the big release day. That means:
>
> - Saturday: last feature-level changes that should be done before beta,
> e.g. removal of packaging
> - Sunday: final feature freeze, bug fixing
> - Monday: focus on stability of the buildbots, even unstable ones
> - Tuesday: forking of the 3.3.0b1 release clone, tagging, start
> of binary building

I'd like to get the C implementation of the timing safe compare_digest
into 3.3. http://bugs.python.org/issue15061

The patch went to several incarnations and I implemented input from
Antoine, Serhiy and others. The function finally ended up as private
function in the operator module because the _hashlib module isn't
available without openssl and a new module for a single function is
kinda overkill.

Christian

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

g.brandl-nospam at gmx

Jun 23, 2012, 1:45 PM

Post #9 of 16 (335 views)
Permalink

Re: 3.3 release plans [In reply to]

-------- Original-Nachricht --------
> Datum: Sat, 23 Jun 2012 21:55:55 +0200
> Von: Christian Heimes <lists [at] cheimes>
> An: python-dev [at] python
> Betreff: Re: [Python-Dev] 3.3 release plans

> Am 23.06.2012 12:54, schrieb g.brandl-nospam [at] gmx:
> > Hi all,
> >
> > now that the final PEP scheduled for 3.3 is final, we're entering
> > the next round of the 3.3 cycle.
> >
> > I've decided to make Tuesday 26th the big release day. That means:
> >
> > - Saturday: last feature-level changes that should be done before beta,
> > e.g. removal of packaging
> > - Sunday: final feature freeze, bug fixing
> > - Monday: focus on stability of the buildbots, even unstable ones
> > - Tuesday: forking of the 3.3.0b1 release clone, tagging, start
> > of binary building
>
> I'd like to get the C implementation of the timing safe compare_digest
> into 3.3. http://bugs.python.org/issue15061
>
> The patch went to several incarnations and I implemented input from
> Antoine, Serhiy and others. The function finally ended up as private
> function in the operator module because the _hashlib module isn't
> available without openssl and a new module for a single function is
> kinda overkill.

Fine with me. You have time until tomorrow to push it.

Georg
--
NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone!
Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

kristjan at ccpgames

Jun 23, 2012, 5:06 PM

Post #10 of 16 (340 views)
Permalink

Re: 3.3 release plans [In reply to]

As long as we are _before_ feature freeze, I would have thought it fine. Also, I'm sure we could allow ourselves some flexibility, after all, it is we that make these schedules, not the other way round.

But no matter. Condition variable wakeup has been sluggish for many years, I'm sure our users can wait a few more. Meanwhile, the patch is there for those who want it.

Cheers,
K
________________________________________
Frá: python-dev-bounces+kristjan=ccpgames.com [at] python [python-dev-bounces+kristjan=ccpgames.com [at] python] fyrir hönd Antoine Pitrou [solipsis [at] pitrou]
Sent: 23. júní 2012 12:37
To: python-dev [at] python
Efni: Re: [Python-Dev] 3.3 release plans

On Sat, 23 Jun 2012 12:32:37 +0000
Kristján Valur Jónsson <kristjan [at] ccpgames> wrote:
> Au contraire, it is actually a very major improvement, the result of pretty extensive profiling, see http://blog.ccpgames.com/kristjan/2012/05/25/optimizing-python-condition-variables-with-telemetry/

It might be. But to evaluate it, we have to digest a long technical blog
post, then carefully review the patch (and perhaps even re-do
some measurements). You understand that it's not reasonable to do so
just one day before feature freeze.

Regards

Antoine.
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/kristjan%40ccpgames.com
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

eric at trueblade

Jun 24, 2012, 8:05 AM

Post #11 of 16 (331 views)
Permalink

Re: 3.3 release plans [In reply to]

On 06/23/2012 06:54 AM, g.brandl-nospam [at] gmx wrote:
> I've decided to make Tuesday 26th the big release day. That means:
>
> - Saturday: last feature-level changes that should be done before beta,
> e.g. removal of packaging
> - Sunday: final feature freeze, bug fixing

What's your timeframe for bug fixes today? I'd very much like to fix
http://bugs.python.org/issue15039, but it will probably take me another
2 hours or so.

Eric.

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

solipsis at pitrou

Jun 24, 2012, 8:27 AM

Post #12 of 16 (327 views)
Permalink

Re: 3.3 release plans [In reply to]

On Sun, 24 Jun 2012 11:05:35 -0400
"Eric V. Smith" <eric [at] trueblade> wrote:
> On 06/23/2012 06:54 AM, g.brandl-nospam [at] gmx wrote:
> > I've decided to make Tuesday 26th the big release day. That means:
> >
> > - Saturday: last feature-level changes that should be done before beta,
> > e.g. removal of packaging
> > - Sunday: final feature freeze, bug fixing
>
> What's your timeframe for bug fixes today? I'd very much like to fix
> http://bugs.python.org/issue15039, but it will probably take me another
> 2 hours or so.

If it's a bugfix, it's not blocked by the feature freeze at all: you
can commit after beta (but you might want the bugfix to be in the beta).

Regards

Antoine.

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

eric at trueblade

Jun 24, 2012, 8:44 AM

Post #13 of 16 (330 views)
Permalink

Re: 3.3 release plans [In reply to]

On 6/24/2012 11:27 AM, Antoine Pitrou wrote:
>> What's your timeframe for bug fixes today? I'd very much like to fix
>> http://bugs.python.org/issue15039, but it will probably take me another
>> 2 hours or so.
>
> If it's a bugfix, it's not blocked by the feature freeze at all: you
> can commit after beta (but you might want the bugfix to be in the beta).

Indeed, that's what I'm after: the fix in the beta. I'll do my best to
get it in, but obviously it's not a blocker.

Eric.

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

eric at trueblade

Jun 24, 2012, 1:14 PM

Post #14 of 16 (325 views)
Permalink

Re: 3.3 release plans [In reply to]

On 6/24/2012 11:44 AM, Eric V. Smith wrote:
> On 6/24/2012 11:27 AM, Antoine Pitrou wrote:
>>> What's your timeframe for bug fixes today? I'd very much like to fix
>>> http://bugs.python.org/issue15039, but it will probably take me another
>>> 2 hours or so.
>>
>> If it's a bugfix, it's not blocked by the feature freeze at all: you
>> can commit after beta (but you might want the bugfix to be in the beta).
>
> Indeed, that's what I'm after: the fix in the beta. I'll do my best to
> get it in, but obviously it's not a blocker.

And, no surprise: it's harder to fix than I thought. It won't make it in
to the beta.

Eric.
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

ncoghlan at gmail

Jun 24, 2012, 5:32 PM

Post #15 of 16 (323 views)
Permalink

Re: 3.3 release plans [In reply to]

On Mon, Jun 25, 2012 at 6:14 AM, Eric V. Smith <eric [at] trueblade> wrote:
> On 6/24/2012 11:44 AM, Eric V. Smith wrote:
>> On 6/24/2012 11:27 AM, Antoine Pitrou wrote:
>>>> What's your timeframe for bug fixes today? I'd very much like to fix
>>>> http://bugs.python.org/issue15039, but it will probably take me another
>>>> 2 hours or so.
>>>
>>> If it's a bugfix, it's not blocked by the feature freeze at all: you
>>> can commit after beta (but you might want the bugfix to be in the beta).
>>
>> Indeed, that's what I'm after: the fix in the beta. I'll do my best to
>> get it in, but obviously it's not a blocker.
>
> And, no surprise: it's harder to fix than I thought. It won't make it in
> to the beta.

FWIW, the way I'll often handle that kind of change is to temporarily
set it to "release-blocker" (so the RM will at least look at it before
deciding whether or not to proceed with the release), and then drop it
down to "deferred blocker" if I decide it's not going to be ready, but
want to commit to getting it fixed before the *next* release.

Cheers,
Nick.

--
Nick Coghlan | ncoghlan [at] gmail | Brisbane, Australia
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

eric at trueblade

Jun 24, 2012, 5:35 PM

Post #16 of 16 (323 views)
Permalink

Re: 3.3 release plans [In reply to]

On 06/24/2012 08:32 PM, Nick Coghlan wrote:
> On Mon, Jun 25, 2012 at 6:14 AM, Eric V. Smith <eric [at] trueblade> wrote:
>> On 6/24/2012 11:44 AM, Eric V. Smith wrote:
>>> On 6/24/2012 11:27 AM, Antoine Pitrou wrote:
>>>>> What's your timeframe for bug fixes today? I'd very much like to fix
>>>>> http://bugs.python.org/issue15039, but it will probably take me another
>>>>> 2 hours or so.
>>>>
>>>> If it's a bugfix, it's not blocked by the feature freeze at all: you
>>>> can commit after beta (but you might want the bugfix to be in the beta).
>>>
>>> Indeed, that's what I'm after: the fix in the beta. I'll do my best to
>>> get it in, but obviously it's not a blocker.
>>
>> And, no surprise: it's harder to fix than I thought. It won't make it in
>> to the beta.
>
> FWIW, the way I'll often handle that kind of change is to temporarily
> set it to "release-blocker" (so the RM will at least look at it before
> deciding whether or not to proceed with the release), and then drop it
> down to "deferred blocker" if I decide it's not going to be ready, but
> want to commit to getting it fixed before the *next* release.

Thanks. I was going to make it a deferred blocker, but I managed to come
up with a fix in time (I hope!).

Eric.

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads