Changes between Initial Version and Version 1 of Ticket #22922, comment 8


Ignore:
Timestamp:
Jul 23, 2014, 5:08:21 AM (10 years ago)
Author:
Mathieu Agopian

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #22922, comment 8

    initial v1  
    1 I'd like to reopen this, as I believe the error message in its current state isn't very useful.
    2 However, I'm not sure it's a good idea to reopen it, as this ticket is a release blocker, and an "even better" error message maybe isn't that important ;)
     1Scratch that, sorry for the noise, I wasn't on trunk (but on 17c1), and didn't see that this was already fixed, my bad.
    32
    4 Here's an example output:
    5 
    6 {{{
    7 Cannot resolve bases for [<django.db.migrations.state.ModelState object at 0x7fd8e82f45d0>, <django.db.migrations.state.ModelState object at 0x109b8e69f476>]
    8 This can happen if you are inheriting models from an app with migrations (e.g. contrib.auth)
    9  in an app with no migrations; see https://docs.djangoproject.com/en/1.7/topics/migrations/#dependencies for more
    10 }}}
    11 
    12 I think it would be much more useful to have the model names for which the bases could not be resolved, eg:
    13 
    14 {{{['foo.Bar', 'baz.Cruux']}}}
    15 
    16 A proposed modification would be to pass in {{{['{}.{}'.format(ms.app_label, ms.name) for ms in new_unrendered_models]}}} instead of simply {{{new_unrendered_models}}}.
    17 
    18 As a side note, I'm not sure the space in front of " in an app" should be there, as it's just after a line-jump, it could (should?) be removed (just nitpicking ;).
     3I can confirm the error message is now very clear.
Back to Top