Ah, I figured it was a cache as a performance optimization :)<br><br>Thanks Ned!<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Nov 14, 2012 at 1:20 PM, Ned Batchelder <span dir="ltr"><<a href="mailto:ned@nedbatchelder.com" target="_blank">ned@nedbatchelder.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
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.<br>
<br>
--Ned.<div><div class="h5"><br>
<br>
<div>On 11/14/2012 3:59 AM, Laurens Van
Houtven wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">Hi,<br>
<br>
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.<br>
<br>
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.<br>
<br>
What's it doing there and what's the consequences of removing it?<br clear="all">
<br>
thanks in advance<br>
lvh<br>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
testing-in-python mailing list
<a href="mailto:testing-in-python@lists.idyll.org" target="_blank">testing-in-python@lists.idyll.org</a>
<a href="http://lists.idyll.org/listinfo/testing-in-python" target="_blank">http://lists.idyll.org/listinfo/testing-in-python</a>
</pre>
</blockquote>
<br>
</div>
</blockquote></div><br><br clear="all"><br>-- <br>cheers<div>lvh</div><br>
</div>