Testing in Django 1.7 throws warning: RemovedInDjango18Warning

Question

When I do my tests with Django 1.7.1 it throws the next warning:

/usr/local/lib/python2.7/dist-packages/django/test/_doctest.py:59:
RemovedInDjango18Warning: The django.test._doctest module is deprecated;
use the doctest module from the Python standard library instead.
RemovedInDjango18Warning)

I also tried adding in the settings.py file this line:

TEST_RUNNER = 'django.test.runner.DiscoverRunner'

But still throws the warning.

I write down the code from my test model file:

from django.test import TestCase
from myproject import tests, models


class TestModels(TestCase):

    def test_rol(self):
        rol = tests.create_rol()
        rol.save()

        self.assertTrue(isinstance(rol, models.Rol))
        self.assertEqual(rol.name, rol.__unicode__())

I have read the docs from the Django Web page: https://docs.djangoproject.com/en/1.7/topics/testing/overview/ but still can't get a solution.

I am using Django-nose.

How can I solve this?

Thanks

Daniel Hawkins · Accepted Answer · 2014-12-09T16:43:11.527

4

This is a problem in the django-nose package (see GitHub issue #149). It has been fixed in master, but there is no PyPI release for it yet. For now, if you don't want to see the warning, you can point your requirements.txt file to the fixed version:

-e git://github.com/django-nose/django-nose.git@154b663097e8f3131fe5d1cdd8a8df2e388450ac#egg=django_nose

... instead of ...

django-nose==1.2

Update: django-nose 1.3 has been released and contains this fix.

edited Dec 09 '14 at 16:43

answered Nov 07 '14 at 15:23

Daniel Hawkins

1,165
13
12

pip install -e git... Is it? – Víctor M Nov 07 '14 at 17:21
@VíctorM yes, if you're just running a single command (not adding the dependency to `requirements.txt`), that is correct. – Daniel Hawkins Nov 14 '14 at 17:49
1

now that django-nose 1.3 is released, please use it like django-nose==1.3 – Antony Dec 06 '14 at 18:23

score 1 · Answer 2 · answered Nov 07 '14 at 15:21

1

It looks like this is a django-nose issue: see here.

So, just ignore it. Presumably it will be fixed before you're actually using Django 1.8.

answered Nov 07 '14 at 15:21

Kevin Christopher Henry

46,175
7
116
102

Testing in Django 1.7 throws warning: RemovedInDjango18Warning

2 Answers2