On Wed, Sep 2, 2009 at 08:19, Boya Sun<bxs187 at case.edu> wrote: > Dear Developers, > > I am a Ph.D student from Case Western Reserve University, specialized at > software engineering. Our recent approach analyzes bugs that are being > fixed in the issue database, and tries to discover any latent bug instances > that are the same as the fixed bug but are left unfixed. We have found some > spurious code in your project in this approach, and pointed out these code > by comments (sometimes also with patches) to the fixed bugs in the issue DB > from which it is discovered as follows: > > Issue 6817: http://bugs.python.org/issue6817 (A new issue, created following > Amaury's comments) > Issue 2620: http://bugs.python.org/issue2620 > Issue 3139: http://bugs.python.org/issue3139 > Issue 5705: http://bugs.python.org/issue5705 I quickly re-opened 2620 and 5705 so we don't lose track of the fact that new code has been attached. -Brett
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