I refer to the following line of code:
https://github.com/django/django/blob/181fb60159e54d442d3610f4afba6f066a6dac05/django/contrib/auth/management/__init__.py#L86
--
Ticket URL: <https://code.djangoproject.com/ticket/30410>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* status: new => closed
* resolution: => wontfix
Comment:
Unless I'm missing something these messages will only be displayed during
tests if `--verbosity=3` as the test command calls `migrate` with
`verbosity - 1` and these messages are only displayed
[https://github.com/django/django/blob/181fb60159e54d442d3610f4afba6f066a6dac05/django/contrib/auth/management/__init__.py#L84-L86
if verbosity >=2] just like content type creation message.
Given `--verbosity=3` is the maximum level and should be synonym of
''print everything'' I don't think adding an extra test option to disable
these particular messages is worth it. If you really want to disable them
during tests only you could unregister the `post_migrate` signals in your
test runner class setup with one that always pass a different `verbosity`.
--
Ticket URL: <https://code.djangoproject.com/ticket/30410#comment:1>