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 amaury.forgeotdarc, benjamin.peterson, gvanrossum, pitrou, pjenvey, r.david.murray, vinay.sajip
Date 2009-10-14.22:32:53
SpamBayes Score 2.3126223e-11
Marked as misclassified No
Message-id <Pine.LNX.4.64.0910141827420.18193@kimball.webabinitio.net>
In-reply-to <881066.76475.qm@web25803.mail.ukl.yahoo.com>
Content
On Wed, 14 Oct 2009 at 21:46, Vinay Sajip wrote:
> Vinay Sajip <vinay_sajip@yahoo.co.uk> added the comment:
>> Guido van Rossum  added the comment:
>>
>> (I don't know why the tracker reopened the issue when I added a comment.
>> Anyway, is the fix going into 2.6.4 or will it have to wait for 2.6.5?)

If a ticket is set to pending, any comment addition changes it back
to open.  The idea is that you set a ticket to 'pending feedback',
and if there is no feedback for time X, the ticket gets closed.
(An auto-close-pending feature has been proposed, but I don't think it
has been implemented yet.)

> In terms of when the fix goes in, I guess it's Barry's call.

Well, your commit to the 2.6 branch puts it into the next RC unless
someone (eg Barry) reverts it.
History
Date User Action Args
2009-10-14 22:32:55r.david.murraysetrecipients: + r.david.murray, gvanrossum, vinay.sajip, amaury.forgeotdarc, pitrou, pjenvey, benjamin.peterson
2009-10-14 22:32:53r.david.murraylinkissue7120 messages
2009-10-14 22:32:53r.david.murraycreate