Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Python bug report on SF, what now?

0 views
Skip to first unread message

Irmen de Jong

unread,
Nov 27, 2003, 3:38:25 PM11/27/03
to
Hi
I've submitted a bug report on Sourceforge
(http://sourceforge.net/tracker/?func=detail&aid=839496&group_id=5470&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

unread,
Nov 27, 2003, 3:40:07 PM11/27/03
to
Irmen de Jong <irmen@-NOSPAM-REMOVETHIS-xs4all.nl> writes:
> Should I have assigned it to somebody, or will
> it be noticed 'automagically'...?

Neither. One of the maintainers will assign it manually.

Martin v. Löwis

unread,
Nov 27, 2003, 5:01:56 PM11/27/03
to
Irmen de Jong <irmen@-NOSPAM-REMOVETHIS-xs4all.nl> writes:

> Hi
> I've submitted a bug report on Sourceforge
> (http://sourceforge.net/tracker/?func=detail&aid=839496&group_id=5470&atid=105470)
> but am wondering what to do next?
>
> Should I have assigned it to somebody, or will
> it be noticed 'automagically'...?

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

unread,
Nov 27, 2003, 5:25:34 PM11/27/03
to
Martin v. Löwis wrote:

> 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.

[...]

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

unread,
Nov 27, 2003, 6:36:30 PM11/27/03
to
mar...@v.loewis.de (Martin v. Löwis) writes:
[...]

> 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
[...]

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


John

Martin v. Löwis

unread,
Nov 28, 2003, 1:27:37 AM11/28/03
to
Irmen de Jong <irmen@-NOSPAM-REMOVETHIS-xs4all.nl> writes:

> 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?

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

unread,
Nov 28, 2003, 1:29:21 AM11/28/03
to
j...@pobox.com (John J. Lee) writes:

> > 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
> [...]
>
> Same for wishlist items with patches? Or should they go in RFE
> (Requests For Enhancement)?

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

0 new messages