[Python-Dev] More Non-Bugs

[Trent Mick]

On Wed, Aug 02, 2000 at 08:31:55AM -0400, Jeremy Hylton wrote:
> >>>>> "MZ" == Moshe Zadka <moshez@math.huji.ac.il> writes:
> 
>   MZ> Hmmmmm.....OK.  But I guess I'll still wait for a goahead from
>   MZ> the PythonLabs team.  BTW: Does anyone know if SF has an e-mail
>   MZ> notification of bugs, similar to that of patches? If so,
>   MZ> enabling it to send mail to a mailing list similar to
>   MZ> patches@python.org would be cool -- it would enable much more
>   MZ> peer review.
> 
> Go ahead and mark as closed bugs that are currently fixed.  If you can
> figure out when they were fixed (e.g. what checkin), that would be
> best.  If not, just be sure that it really is fixed -- and write a
> test case that would have caught the bug.

I think that unless

(1) you submitted the bug or can be sure that "works for me"
    is with the exact same configuration as the person who did; or
(2) you can identify where in the code the bug was and what checkin (or where
    in the code) fixed it

then you cannot close the bug.

This is the ideal case, with incomplete bug reports and extremely stale one
then these strict requirements are probably not always practical.

Trent

-- 
Trent Mick
TrentM@ActiveState.com