Version 1.4 seems to break when django.templates.backends has not been initialized

This is clearly a bug caused by my recent PR.

  Coverage.py warning: Disabling plugin 'django_coverage_plugin.DjangoTemplatePlugin' due to an exception:
 Traceback (most recent call last):
   File "/home/teamcity/.virtualenvs/addgene1.8/local/lib/python2.7/site-packages/coverage/control.py", line 476, in _should_trace_internal
     file_tracer = plugin.file_tracer(canonical)
   File "/home/teamcity/.virtualenvs/addgene1.8/local/lib/python2.7/site-packages/django_coverage_plugin/plugin.py", line 158, in file_tracer
     self.debug_checked = check_debug()
   File "/home/teamcity/.virtualenvs/addgene1.8/local/lib/python2.7/site-packages/django_coverage_plugin/plugin.py", line 56, in check_debug
     if not hasattr(django.template.backends, "django"):

I’ll work though a fix PR in the next two days.

Because of the chicken-and-egg issues of starting, I think the need for a test_project that can be used for full integration testing via subprocess calls is even more vital. There are too many “shenanigans” involved with getting coverage/django startup initialization order reversed and re-run during the current test process.

[clokep]

@garyayo Use the following: pip install https://codeload.github.com/nedbat/django_coverage_plugin/zip/4df203a0908ac638f6c6da2b2e53096eb29506e8

Note that if you already have django-coverage-plugin 1.4.1 installed pip won’t upgrade to the new code because it’s the same version number.

[PamelaM]

@garyayo Could you try with PR https://github.com/nedbat/django_coverage_plugin/pull/38? I think the fix will address both your issue and a number of other, similar ones.

Please let me know if it works for you.

Thanks Pam