bug reporting

Arthur Siegel ajs at ix.netcom.com
Sun Mar 17 19:41:22 EST 2002


In thread  "Still same bug even with email ver. 1.2"

Martin writes -
>If you think you found a bug, submit a bug report.

It could waste time of the developers to have to
weed through false alarm bug reports.  One of the
roles of this list is to vet some of these issues.

I had posted up behavior that I thought could be anything
from my own misunderstanding of fundamentals to
a bug in the core.  Their was only one response on the list -
to the effect that the behavior could be duplicated on his machine, with the
implication that it was unanticipated
behavior from his point of view as well.

The issue was related to overloading operators in a class subbed from the
'complex' built-in - not exactly a high traffic lane, I suspect.

Is the recommendation to submit it as a maybe bug?

>If you know how to fix it, submitting a patch would be even >more
appreciated.

I'm holding out for check-in rights ;)

Art







More information about the Python-list mailing list