#24412: Red migration notice should be printed when running tests without
--verbosity=2
-------------------------------+-----------------------
     Reporter:  pzrq           |      Owner:  nobody
         Type:  Uncategorized  |     Status:  new
    Component:  Migrations     |    Version:  1.8alpha1
     Severity:  Normal         |   Keywords:
 Triage Stage:  Unreviewed     |  Has patch:  0
Easy pickings:  0              |      UI/UX:  0
-------------------------------+-----------------------
 The following quite useful red NOTICE is printed to the command line only
 when running `manage.py test --verbosity=2 --keepdb` (the second time
 after no migrations are run), and thus buried amongst a lot of other
 information:
 
https://github.com/django/django/blob/master/django/core/management/commands/migrate.py#L183-191

   Your models have changes that are not yet reflected in a migration, and
 so won't be applied.
   Run 'manage.py makemigrations' to make new migrations, and then re-run
 'manage.py migrate' to apply them.

 I think it should be print at the default `manage.py test`  (i.e.
 `--verbosity=1`).

 This might be complicated by decrementing the verbosity by 1 when calling
 `migrate` inside `create_test_db`:
 
https://github.com/django/django/blob/master/django/db/backends/base/creation.py#L68

 Though there are only 16 verbosity strings in `migrate.py` (including
 calls to showmigrations and emit_pre_migrate_signal) so the side effects
 from that part should be reasonably traceable.

 Not sure about not printing the first time (i.e. without `--keepdb`)  ...
 any thoughts?

--
Ticket URL: <https://code.djangoproject.com/ticket/24412>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/047.53313c13f5a205538037ff36eeaf9116%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to