[Python-3000] Reminder: last alphas next Wednesday 07-May-2008

Brett Cannon brett at python.org
Fri May 2 04:31:20 CEST 2008


On Thu, May 1, 2008 at 1:26 PM, Barry Warsaw <barry at python.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
>  Hash: SHA1
>
>  This is a reminder that the LAST planned alpha releases of Python 2.6 and
> 3.0 are scheduled for next Wednesday, 07-May-2008.  Please be diligent over
> the next week so that none of your changes break Python.  The stable
> buildbots look moderately okay, let's see what we can do about getting them
> all green:
>
>  http://www.python.org/dev/buildbot/stable/
>
>  We have a few showstopper bugs, and I will be looking at these more
> carefully starting next week.
>
>
> http://bugs.python.org/issue?@columns=title,id,activity,versions,status&@sort=activity&@filter=priority,status&@pagesize=50&@startwith=0&priority=1&status=1&@dispname=Showstoppers
>
>  Time is running short to get any new features into Python 2.6 and 3.0.  The
> release after this one is scheduled to be the first beta release, at which
> time we will institute a feature freeze.  If your feature doesn't make it in
> by then, you'll have to wait until 2.7/3.1.  If there is something that
> absolutely must go into 2.6/3.0 be sure that there is a bug issue open for
> it and that the Priority is set to 'release blocker'.  I may reduce it to
> critical for the next alpha, but we'll review all the release blocker and
> critical issues for the first 2.6 and 3.0 beta releases.

I just closed the release blocker I created (the
backwards-compatibility issue with warnings.showwarning() ). I would
like to add a PendingDeprecationWarning (or stronger) to 2.6 for
showwarning() implementations that don't support the optional 'line'
argument. I guess the best way to do it in C code would be to see if
PyFunction_GetDefaults() returns a tuple of length two (since
showwarning() already has a single optional argument as it is).

Anyone have an issue with me doing this? Is PendingDeprecationWarning
safe enough for 2.6? Or should this be a 3.0-only thing with a
DeprecationWarning?

-Brett


More information about the Python-3000 mailing list