-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Okay, this is it: please no more commits to the py3k branch for now.
Also, for the remainder of the time until final, please make sure there is an issue for each change you want to make containing the patch (which was already the case for almost all changes after rc1 anyway), and assign the issue to me for sign-off after review.
Changes to the "What's new" are exempt, but I would love some volunteers to read through the document and note any issues or typos.
cheers, Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1FNM4ACgkQN9GcIYhpnLB20wCfUHDP6xAy3jOj2egp+IsYhA8r fYkAnR5gSiXv79y7UXLH97zpcUMcAXHV =4g0D -----END PGP SIGNATURE-----
On Sun, Jan 30, 2011 at 7:52 PM, Georg Brandl <georg@python.org> wrote:
Changes to the "What's new" are exempt, but I would love some volunteers to read through the document and note any issues or typos.
I put some comments up at http://bugs.python.org/issue11071.
Mostly minor typo stuff, but there are a couple of additional logging changes that I think should be highlighted: libraries (such as concurrent.futures) to reliably use the logging
- the new "handler of last resort" functionality, which allows
module to report unraisable exceptions.
- the new logging HOWTO in the docs which should hopefully make it much easier for people to start making effective use of the package
Cheers, Nick.
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 30.01.2011 14:49, schrieb Nick Coghlan:
On Sun, Jan 30, 2011 at 7:52 PM, Georg Brandl <georg@python.org> wrote:
Changes to the "What's new" are exempt, but I would love some volunteers to read through the document and note any issues or typos.
I put some comments up at http://bugs.python.org/issue11071.
Mostly minor typo stuff, but there are a couple of additional logging changes that I think should be highlighted: libraries (such as concurrent.futures) to reliably use the logging
- the new "handler of last resort" functionality, which allows
module to report unraisable exceptions.
- the new logging HOWTO in the docs which should hopefully make it much easier for people to start making effective use of the package
Thanks for doing this!
Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1Fcj4ACgkQN9GcIYhpnLAs/gCeOTGeKJQJitFea51uXNNPJAVi qUcAnjfrfm10+EzW1v93oYLaag0zu4h5 =jpsK -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 30.01.2011 10:52, schrieb Georg Brandl:
Okay, this is it: please no more commits to the py3k branch for now.
Also, for the remainder of the time until final, please make sure there is an issue for each change you want to make containing the patch (which was already the case for almost all changes after rc1 anyway), and assign the issue to me for sign-off after review.
Changes to the "What's new" are exempt, but I would love some volunteers to read through the document and note any issues or typos.
OK, the branch is now unfrozen again, but please remember the policy above.
Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1FzkkACgkQN9GcIYhpnLBjWgCePiwOg8dohZ0Di6w5ynB2+mw4 MFcAn2ui6oSxXncsbAn0jEwsrR1HBAD1 =MkDy -----END PGP SIGNATURE-----
Hi Georg,
Georg Brandl <georg <at> python.org> writes:
Am 30.01.2011 10:52, schrieb Georg Brandl:
Okay, this is it: please no more commits to the py3k branch for now.
Also, for the remainder of the time until final, please make sure there is an issue for each change you want to make containing the patch (which was already the case for almost all changes after rc1 anyway), and assign the issue to me for sign-off after review.
Changes to the "What's new" are exempt, but I would love some volunteers to read through the document and note any issues or typos.
OK, the branch is now unfrozen again, but please remember the policy above.
Does this apply to doc changes, too? I want to make some additions to the SocketHandler docs - about functionality which has been in there for a long time but, due to an oversight, never got documented. Since it's long overdue, it can certainly wait a little longer :-)
Regards,
Vinay Sajip
Am 12.02.2011 15:28, schrieb Vinay Sajip:
Hi Georg,
Georg Brandl <georg <at> python.org> writes:
Am 30.01.2011 10:52, schrieb Georg Brandl:
Okay, this is it: please no more commits to the py3k branch for now.
Also, for the remainder of the time until final, please make sure there is an issue for each change you want to make containing the patch (which was already the case for almost all changes after rc1 anyway), and assign the issue to me for sign-off after review.
Changes to the "What's new" are exempt, but I would love some volunteers to read through the document and note any issues or typos.
OK, the branch is now unfrozen again, but please remember the policy above.
Does this apply to doc changes, too? I want to make some additions to the SocketHandler docs - about functionality which has been in there for a long time but, due to an oversight, never got documented. Since it's long overdue, it can certainly wait a little longer :-)
If you can manage, it would be nice to upload the patch somewhere and let me review it quickly.
Georg
Georg Brandl <g.brandl <at> gmx.net> writes:
If you can manage, it would be nice to upload the patch somewhere and let me review it quickly.
Here's the patch:
https://gist.github.com/824644
I know you'll be busy so I completely understand if you don't have time to review it :-)
Thanks,
Vinay Sajip
On Sun, Feb 13, 2011 at 12:22:46PM +0000, Vinay Sajip wrote:
Here's the patch:
I think you missed the rc3 freeze email. :)
-- Senthil
On 13/02/2011 13:42, Senthil Kumaran wrote:
On Sun, Feb 13, 2011 at 12:22:46PM +0000, Vinay Sajip wrote:
Here's the patch:
I think you missed the rc3 freeze email. :)
It's just a doc patch that Georg gave permission for - or did you mean something else?
Michael
-- http://www.voidspace.org.uk/
May you do good and not evil May you find forgiveness for yourself and forgive others May you share freely, never taking more than you give. -- the sqlite blessing http://www.sqlite.org/different.html
On Sun, Feb 13, 2011 at 9:44 PM, Michael Foord <mfoord@python.org> wrote:
On 13/02/2011 13:42, Senthil Kumaran wrote:
On Sun, Feb 13, 2011 at 12:22:46PM +0000, Vinay Sajip wrote:
Here's the patch:
I think you missed the rc3 freeze email. :)
It's just a doc patch that Georg gave permission for - or did you mean something else?
Oh, I had not check the contents of the patch. But I followed the discussion and timeline for this thread which was relevant for rc2. Georg had sent the rc3 freeze email just before this (which had some strict criteria on changes which can go in) and I thought Vinay missed that email.
-- Senthil
Am 13.02.2011 14:42, schrieb Senthil Kumaran:
On Sun, Feb 13, 2011 at 12:22:46PM +0000, Vinay Sajip wrote:
Here's the patch:
I think you missed the rc3 freeze email. :)
He didn't actually commit it, but I will do after rc3 is out the door.
Georg
participants (6)
-
Georg Brandl -
Georg Brandl -
Michael Foord -
Nick Coghlan -
Senthil Kumaran -
Vinay Sajip