-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We had a lot of discussion recently about changing the release
schedule and splitting Python 2.6 and 3.0. There was general
consensus that this was a good idea, in order to hit our October 1
deadline for Python 2.6 final at least.
There is on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 12, 2008, at 9:19 AM, Edward K. Ream wrote:
On Fri, Sep 12, 2008 at 7:54 AM, Barry Warsaw <[EMAIL PROTECTED]>
wrote:
We had a lot of discussion recently about changing the release
schedule and
splitting Python 2.6 and 3.0. There was gen
ACTIVITY SUMMARY (09/05/08 - 09/12/08)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
2019 open (+32) / 13652 closed (+30) / 15671 total (+62)
Open issues with patches: 637
Average
On Fri, Sep 12, 2008 at 7:54 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> We had a lot of discussion recently about changing the release schedule and
> splitting Python 2.6 and 3.0. There was general consensus that this was a
> good idea, in order to hit our October 1 deadline for Python 2.6 fin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Python development team and the Python community, I
am happy to announce the first release candidate for Python 2.6.
This is a release candidate, so while it is not suitable for
production environments, we strongly encourage you
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=93818
User mru changed the following:
What|Old value |New value
