Missing DJANGO_SETTINGS_MODULE

[jonashaag]

With empty .coveragerc:

$ coverage run foo/manage.py test bar
[...works...]

With django-coverage-plugin in .coveragerc:

[run]
plugins =
  django_coverage_plugin

$ coverage run foo/manage.py test bar
[...]
django.core.exceptions.ImproperlyConfigured: Requested setting TEMPLATES, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.

manage.py is unmodified (generated by Django).

[nedbat]

Can you show the complete error report with traceback?

[jonashaag]

Sure. Actually from the traceback it looks more like django-coverage-plugin wants the use settings before manage.py has loaded the environment variable; changing the title accordingly.

Traceback (most recent call last):
  File "/my/project/.tox/py35-django18/bin/coverage", line 11, in <module>
    sys.exit(main())
  File "/my/project/.tox/py35-django18/lib/python3.5/site-packages/coverage/cmdline.py", line 741, in main
    status = CoverageScript().command_line(argv)
  File "/my/project/.tox/py35-django18/lib/python3.5/site-packages/coverage/cmdline.py", line 481, in command_line
    return self.do_run(options, args)
  File "/my/project/.tox/py35-django18/lib/python3.5/site-packages/coverage/cmdline.py", line 610, in do_run
    self.coverage.erase()
  File "/my/project/.tox/py35-django18/lib/python3.5/site-packages/coverage/control.py", line 709, in erase
    self._init()
  File "/my/project/.tox/py35-django18/lib/python3.5/site-packages/coverage/control.py", line 218, in _init
    self.plugins = Plugins.load_plugins(self.config.plugins, self.config, self.debug)
  File "/my/project/.tox/py35-django18/lib/python3.5/site-packages/coverage/plugin_support.py", line 49, in load_plugins
    coverage_init(plugins, options)
  File "/my/project/.tox/py35-django18/lib/python3.5/site-packages/django_coverage_plugin/__init__.py", line 11, in coverage_init
    reg.add_file_tracer(DjangoTemplatePlugin())
  File "/my/project/.tox/py35-django18/lib/python3.5/site-packages/django_coverage_plugin/plugin.py", line 122, in __init__
    check_debug()
  File "/my/project/.tox/py35-django18/lib/python3.5/site-packages/django_coverage_plugin/plugin.py", line 52, in check_debug
    templates = getattr(settings, 'TEMPLATES', [])
  File "/my/project/.tox/py35-django18/lib/python3.5/site-packages/django/conf/__init__.py", line 48, in __getattr__
    self._setup(name)
  File "/my/project/.tox/py35-django18/lib/python3.5/site-packages/django/conf/__init__.py", line 42, in _setup
    % (desc, ENVIRONMENT_VARIABLE))
django.core.exceptions.ImproperlyConfigured: Requested setting TEMPLATES, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.

[jonashaag]

Note that this worked in 1.1 and broke in 1.2, I can bisect the commit for you if you want

[nedbat]

@jonashaag more details about how reproduce this, or which commit it was, would be great.

[jonashaag]

Just use startproject, startapp, and then the settings I show above.

[jonashaag]

Bump

[keimlink]

@jonashaag Did you manage to identify the exact commit that causes the error?

[jonashaag]

@keimlink Yes but I don't remember which one it was, you can simply run git bisect to find it

[rfleschenberg]

bisect points at 0085fb8

[nedbat]

I'll be able to jump into this more easily with a zipfile or specific instructions about how to reproduce it.

[rfleschenberg]

Steps to reproduce:

mkvirtualenv issue-18
pip install git+https://github.com/nedbat/django_coverage_plugin.git
django-admin startproject myprj
printf "[run]\nplugins = \n  django_coverage_plugin\n" > .coveragerc
coverage run myprj/manage.py test

[rfleschenberg]

Actually, it works fine if you run from the directory where manage.py is located. I think that is expected. You should always run manage.py from its direct parent directory. Otherwise, DJANGO_SETTINGS_MODULE will point at the wrong target (unless you take some other measure to get your project into sys.path).

@jonashaag: does it work if you cd into foo and run ./manage.py test?

[rfleschenberg]

Eh, sorry. My comment above about having to run manage.py from its parent dir is wrong. DJANGO_SETTINGS_MODULE is relative to the location of manage.py. I really shouldn't debug things at this time of the day :-/

But at least I found out that the current directory has something to do with it. Happy debugging ;)