[Python-Dev] memory leaks in 2.2 (original) (raw)
Guido van Rossum guido@python.org
Thu, 06 Dec 2001 08:48:25 -0500
- Previous message: [Python-Dev] memory leaks in 2.2
- Next message: [Python-Dev] memory leaks in 2.2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
As for the things we should change: I believe it is pointless to sit on a report for a long time without doing anything about this. If nothing happens for a year, the person that was assigned this report likely won't do anything about it for the next months, either. Unassigning things you know you won't do is particularly important for patches, but to a degree also important for bug reports. It signals that somebody else may need to step forward, or that some deity should just decide on the fate of this report.
Yup. We've missed important bugs in the past because they happened to be assigned to someone who didn't care. (I noticed that Jack recommended some bug reporter to assign bugs to him rather than let them sit anonymously. That may work in his case, but in general it's the wrong thing to do.)
--Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-Dev] memory leaks in 2.2
- Next message: [Python-Dev] memory leaks in 2.2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]