<div dir="ltr">Thanks, Jason. That makes sense.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 10, 2014 at 6:55 PM, Jason Michalski <span dir="ltr"><<a href="mailto:armooo@armooo.net" target="_blank">armooo@armooo.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi David,<br>
<br>
It looks like manage.py runfcgi defaults to using a pre-forking mode<br>
where a pool of processes handle the requests. By default coverage is<br>
only able to install its trace function in the main process. Also the<br>
threaded mode of flup uses the low level thread module which coverage<br>
also can not track. Directions for tracking subprocess coverage are<br>
here <a href="http://nedbatchelder.com/code/coverage/subprocess.html" target="_blank">http://nedbatchelder.com/code/coverage/subprocess.html</a> .<br>
-- jason<br>
<div><div class="h5"><br>
<br>
On Mon, Mar 10, 2014 at 3:50 PM, David Wyde <<a href="mailto:david.wyde@gmail.com">david.wyde@gmail.com</a>> wrote:<br>
> Greetings,<br>
><br>
> I can't seem to get coverage.py to work with Django + FastCGI (manage.py<br>
> runfcgi). The alternative `coverage run manage.py runserver --noreload`<br>
> works.<br>
><br>
> A sample project is available at <a href="https://github.com/dwyde/cover_django" target="_blank">https://github.com/dwyde/cover_django</a> -<br>
> please see the README for full details.<br>
><br>
> Any ideas?<br>
><br>
><br>
> Thanks,<br>
><br>
> David<br>
><br>
</div></div>> _______________________________________________<br>
> testing-in-python mailing list<br>
> <a href="mailto:testing-in-python@lists.idyll.org">testing-in-python@lists.idyll.org</a><br>
> <a href="http://lists.idyll.org/listinfo/testing-in-python" target="_blank">http://lists.idyll.org/listinfo/testing-in-python</a><br>
><br>
</blockquote></div><br></div>