A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2005-April/052507.html below:

[Python-Dev] New bug, directly assigned, okay?

[Python-Dev] New bug, directly assigned, okay?Irmen de Jong irmen at xs4all.nl
Sat Apr 2 18:04:21 CEST 2005
Nick Coghlan wrote:
> Irmen de Jong wrote:
> 
>> I just added a new bug on SF (1175396) and because I think
>> that it is related to other bugs that were assigned to
>> Walter Doerwald, I assigned this new bug directly to Walter too.
>>
>> Is that good practice or does someone else usually assign SF bugs to
>> people?
> 
> 
> I've certainly done that a few times myself - I figure that even if I
> get it wrong, the recipient will either pass it on to a more appropriate
> person, or simply revert it back to unassigned.

Ah, okay.

> I usually try to put in a comment to say *why* I've assigned it the way
> I have, though. Picking an assignee at random should probably be
> discouraged, but if there is someone that makes sense, then I don't see
> a problem with asking them to look at it directly.

Yep, that's what I've done.
In my bug report (about codecs.readline) I referenced the two
other bugs related to it (those were assigned to Walter).


Thanks,
Irmen.
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4