Guido> But there's soooooo much data... How do we find the gems?
Guido> Should we just look at one file per day and try to add testcases
Guido> that get rid of the ##### comments? Is there a way to sort the
Guido> files based on the number or significance of the ##### comments?
All I referred you to yesterday (it was late...) was a CVS tree in which I
had built the interpreter with the necessary flags, run regrtest.py, then
generated coverage files. The next step is to generate one or more pages of
coverage summaries. Then you'll be able to browse something like
http://www.musi-cal.com/~skip/python/Python/dist/src/lines.html
http://www.musi-cal.com/~skip/python/Python/dist/src/branches.html
and zero in on those files with lower than desired coverage.
Skip
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