[TIP] Problems with coverage.py + Django + FastCGI
david.wyde at gmail.com
Mon Mar 10 19:51:42 PDT 2014
Thanks, Jason. That makes sense.
On Mon, Mar 10, 2014 at 6:55 PM, Jason Michalski <armooo at armooo.net> wrote:
> Hi David,
> It looks like manage.py runfcgi defaults to using a pre-forking mode
> where a pool of processes handle the requests. By default coverage is
> only able to install its trace function in the main process. Also the
> threaded mode of flup uses the low level thread module which coverage
> also can not track. Directions for tracking subprocess coverage are
> here http://nedbatchelder.com/code/coverage/subprocess.html .
> -- jason
> On Mon, Mar 10, 2014 at 3:50 PM, David Wyde <david.wyde at gmail.com> wrote:
> > Greetings,
> > I can't seem to get coverage.py to work with Django + FastCGI (manage.py
> > runfcgi). The alternative `coverage run manage.py runserver --noreload`
> > works.
> > A sample project is available at https://github.com/dwyde/cover_django -
> > please see the README for full details.
> > Any ideas?
> > Thanks,
> > David
> > _______________________________________________
> > 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...
More information about the testing-in-python