[Python-Dev] bug triage
brian.curtin at gmail.com
Wed Jan 6 15:57:42 CET 2010
On Wed, Jan 6, 2010 at 06:57, Nick Coghlan <ncoghlan at gmail.com> wrote:
> I believe someone (Daniel Diniz, maybe?) did do a pass over those some
> time in the last 12 months, so most of the obviously irrelevant ones
> that are that old should already be gone. Not to say it isn't worth
> doing another pass, just saying not to get disheartened if there aren't
> many that can be readily closed.
> There are at least a few still kicking around just because they're
> difficult to deal with (there's an ancient one to do with one of the
> ways circular imports can fail that I occasionally go back and reread
> before moving on to something more tractable).
On the topic of bugs that can be readily closed (literally), I've recently
come across a number of issues which appear to be sitting in a patch or
review stage, but their patches have been committed and the issue remains
open. What is the best course of action there? I'd just go ahead and close
the issue myself but I don't have tracker privileges.
I'm willing to help out with another Daniel Diniz-esque triage sweep if that
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev