[TIP] What's status.dat doing in coverage.py's HTML report?

Ned Batchelder ned at nedbatchelder.com
Wed Nov 14 04:20:53 PST 2012

Creating the HTML report can be time-consuming.  But generally, the 
report changes very little between successive runs of coverage.py. 
status.dat records hashes of the source files and their coverage data, 
so they can be skipped if they haven't changed.  In typical usage, this 
makes the HTML report much faster to generate.  There's nothing 
sensitive in the file, I would leave it.


On 11/14/2012 3:59 AM, Laurens Van Houtven wrote:
> Hi,
> I've recently moved to Fossil. It has this feature where some files 
> from the repository (or even the current checkout) can be served by 
> the web server. This is great for showing stuff like build output, 
> including coverage data.
> So I changed my coverage.py line to dump output in that directory and 
> put the output under source control... And then I saw that this 
> status.dat file, filled with binary data got added.
> What's it doing there and what's the consequences of removing it?
> thanks in advance
> lvh
> _______________________________________________
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
> http://lists.idyll.org/listinfo/testing-in-python

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20121114/b08967a9/attachment.html>

More information about the testing-in-python mailing list