Skip Montanaro <skip@pobox.com> writes: > Done. Sunday morning, 7AM, it compares the local info with the displayed > into and send a summary mail to python-dev. The first run this Sunday will > be thin because the database was last updated just a few minutes ago. Note > that bugs or patches that are opened and closed quickly won't be seen, since > all I'm doing is scraping the bug/patch browser. I don't think that's a big > deal though. Easy fixes aren't what people need to be alerted to. If feasible, you might extract what SF gives as the total number of bugs/patches, and reporting the number of bugs that you did not account for. Regards, Martin
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