id summary reporter owner description type status component version severity resolution keywords cc stage has_patch needs_docs needs_tests needs_better_patch easy ui_ux 11696 validate command in 1.1 hides errors in models that used to be shown martin maney Luc Saffre "Given a trivial error in a model, running ""django manage.py validate"" with Django 1.0.2 diagnoses the error, a spelling error/typo, very clearly (traceback trimmed, obviously): {{{ File ""/home/rocketry/rocketry/../rocketry/event/models.py"", line 5, in [[br]] from django.contrib.contentypes.models import ContentType[[br]] ImportError: No module named contentypes.models }}} With Django 1.1, it does its damndest to make you think there's something wrong in a completely different direction, making diagnosis damned near impossible: $ python manage.py validate[[br]] Error: One or more models did not validate:[[br]] club.shiftworked: 'event' has a relation with model event.Event, which has either not been installed or is abstract.[[br]] club.attendance: 'event' has a relation with model event.Event, which has either not been installed or is abstract. This is a clear regression in usability, at least for those of us whose code is not always flawless. BTW, at least in this case 1.1 produces the same unhelpful message for the shell command, so I don't know how you're supposed to fix bugs in models.py unless you have an older version of Django to hand." closed Database layer (models, ORM) 1.1 fixed Accepted 1 0 1 0 0 0