[Python-Dev] About resolution “accepted” on the tracker

Georg Brandl g.brandl at gmx.net
Mon Oct 18 21:31:24 CEST 2010

Am 18.10.2010 21:28, schrieb Michael Foord:
>   On 18/10/2010 20:24, Georg Brandl wrote:
>> Am 18.10.2010 21:04, schrieb Michael Foord:
>>>    On 18/10/2010 19:18, Georg Brandl wrote:
>>>> Am 18.10.2010 20:11, schrieb Barry Warsaw:
>>>>> On Oct 18, 2010, at 04:04 PM, Éric Araujo wrote:
>>>>>> Raymond Hettinger noticed on the tracker that there are different
>>>>>> interpretations of the “accepted” resolution:
>>>>>>> Traditionally it denotes an approved patch, not a agreement that the
>>>>>>> bug is valid.
>>>>> I'm with Raymond; I've always used 'accepted' to mean an approved patch.
>>>> Same here.  I think of the resolution as only relevant when the issue
>>>> status is closed (or pending, of course).
>>> Whilst I agree we lack a "status" (resolution is probably not right)
>>> that says either this bug has been verified as genuine and needs fixing
>>> or for a feature request that it has been agreed that the feature can be
>>> added but not yet got as far as a completed patch.
>> Don't we have "stage" for that (at the moment at least)?
> Which stage do you have in mind, "patch needed"?
> This is currently used for any issue that lacks a patch and doesn't mean 
> that an issue has been accepted as "valid" in any way.

This is probably sophistry, but if an issue is invalid, it doesn't need
a patch :)  The first stage seems to be "unit test needed" anyway, which
sounds to me a bit like "needs to be checked for reproducibility/validity".


Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.

More information about the Python-Dev mailing list