On Mon, 8 Nov 2004 20:38:31 +0100, Johannes Gijsbers <jlg at dds.nl> wrote: > Sounds good to me, with the following caveat. Before adding this > comment, do a casual check whether the bug has been reproduced by > another developer and/or whether you can reproduce it yourself. Don't > spend too much time on it, but just check whether it's obvious the bug > still exists. Wouldn't want to see bugs like http://python.org/sf/548176 > or http://python.org/sf/531205 get closed because of lack of response. FWIW, I tested these two bugs on 2.3 and 2.4b2, and added an appropriate comment. If there are any other such bugs, it's easy enough to do this yourself. Paul
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