This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients abarry, berker.peksag, eryksun, gvanrossum, ppperry, r.david.murray, rhettinger, serhiy.storchaka, steven.daprano
Date 2016-05-31.00:42:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Berker, I don't mind if people mark their own patches for commit review *when they think it is ready for commit*.  (Just as with reviewers, if they start being consistently right, they are ready for commit privs :)  However, a non-committer setting a patch to commit review is waving a hand for attention from a core dev, and that should only be done *after* a patch has been *reviewed* and judged ready for final review before commit.

(I broke my own rule the other day and got in trouble, though...I set a patch to commit review to remind myself to review it rather than because I thought it was commit ready already, and it got committed...)
Date User Action Args
2016-05-31 00:42:10r.david.murraysetrecipients: + r.david.murray, gvanrossum, rhettinger, steven.daprano, berker.peksag, serhiy.storchaka, eryksun, ppperry, abarry
2016-05-31 00:42:10r.david.murraysetmessageid: <>
2016-05-31 00:42:10r.david.murraylinkissue27157 messages
2016-05-31 00:42:08r.david.murraycreate