Python bug report on SF, what now?

[Irmen de Jong]

Hi
I've submitted a bug report on Sourceforge
(http://sourceforge.net/tracker/?func...70&atid=105470)
but am wondering what to do next?

Should I have assigned it to somebody, or will
it be noticed 'automagically' ...?

Sorry for being ignorant in this matter...

--Irmen.

[Paul Rubin]

Re: Python bug report on SF, what now?

Irmen de Jong <irmen@-NOSPAM-REMOVETHIS-xs4all.nl> writes:[color=blue]
> Should I have assigned it to somebody, or will
> it be noticed 'automagically' ...?[/color]

Neither. One of the maintainers will assign it manually.

[Martin v. Löwis]

Re: Python bug report on SF, what now?

Irmen de Jong <irmen@-NOSPAM-REMOVETHIS-xs4all.nl> writes:
[color=blue]
> Hi
> I've submitted a bug report on Sourceforge
> (http://sourceforge.net/tracker/?func...70&atid=105470)
> but am wondering what to do next?
>
> Should I have assigned it to somebody, or will
> it be noticed 'automagically' ...?[/color]

It will be noticed automagically. As it has a patch associated, you
should have submitted it as a patch, though - some of us (including
myself) give patches higher priority, as they indicate that the
submitter is willing to do all the work. If a patch fixes a definite
bug, and it is clearly correct, I'll try to apply it right away (when
I notice it). If it is a patch, and it is dubious (e.g. incomplete, or
the problem is incorrectly described, ...), I'll ask for further
information. If it is a bug report, and it is not for code that I have
written myself, I ignore it.

Regards,
Martin

P.S. I have reclassified it as a patch.

[Irmen de Jong]

Re: Python bug report on SF, what now?

Martin v. Löwis wrote:
[color=blue]
> It will be noticed automagically. As it has a patch associated, you
> should have submitted it as a patch, though - some of us (including
> myself) give patches higher priority, as they indicate that the
> submitter is willing to do all the work.[/color]
[...]

So you're saying that if you find a bug, and have a patch for it,
just submit the patch (with problem description of course) on SF
and forget about the bug tracker?

Anyway thanks Martin for explaining :-)

--Irmen.

[John J. Lee]

Re: Python bug report on SF, what now?

martin@v.loewis .de (Martin v. Löwis) writes:
[...][color=blue]
> It will be noticed automagically. As it has a patch associated, you
> should have submitted it as a patch, though - some of us (including
> myself) give patches higher priority, as they indicate that the[/color]
[...]

Same for wishlist items with patches? Or should they go in RFE
(Requests For Enhancement)?


John

[Martin v. Löwis]

Re: Python bug report on SF, what now?

Irmen de Jong <irmen@-NOSPAM-REMOVETHIS-xs4all.nl> writes:
[color=blue]
> So you're saying that if you find a bug, and have a patch for it,
> just submit the patch (with problem description of course) on SF
> and forget about the bug tracker?[/color]

Right. In principle, you might submit to both the bug report and the
patch tracker, but this is overkill.

Regards,
Martin

[Martin v. Löwis]

Re: Python bug report on SF, what now?

jjl@pobox.com (John J. Lee) writes:
[color=blue][color=green]
> > It will be noticed automagically. As it has a patch associated, you
> > should have submitted it as a patch, though - some of us (including
> > myself) give patches higher priority, as they indicate that the[/color]
> [...]
>
> Same for wishlist items with patches? Or should they go in RFE
> (Requests For Enhancement)?[/color]

Same for wishlist items: They wouldn't be just wishes, but they would
be new features. If the new feature is not universally accepted, you
might need to write a PEP, too.

Regards,
Martin