Changes between Version 7 and Version 8 of BetterErrorMessages


Ignore:
Timestamp:
May 17, 2006, 11:06:53 AM (18 years ago)
Author:
pb@…
Comment:

added app/project name conflict

Legend:

Unmodified
Added
Removed
Modified

  • BetterErrorMessages

    v7 v8  
    11= Better Error Messages =
    22
    3 I'm starting this page as a place to collect error messages that could stand improvement, or which are misleading or confusing in certain contexts. Most of us have had the experience of getting a "weird" message, puzzling it out (perhaps with help from django-users or #django) and then moving on. Later it can be hard to remember what the problem was.
     3This page is a place to collect error messages that could stand improvement, or which are misleading or confusing in certain contexts. Most of us have had the experience of getting a "weird" message, puzzling it out (perhaps with help from django-users or #django) and then moving on. Later it can be hard to remember what the problem was.
    44
    55This is an experiment to see if having a dedicated place to describe these cases as we encounter them can help organize a quality-control effort. Good error messages make for more productive developers. (And it helps newbies be more self-supporting, too.)
    66
    7 Some of these may seem like quick patches but I know that others will take a bit of consideration -- that's why the wiki page rather than individual tickets.
     7Some of these may seem like quick patches but others will take a bit of consideration -- that's why the wiki page rather than individual tickets. Some are more along the lines of "Django Lint" than simple changes to error output.
    88
    99For now, let's try dividing them into sections by major module. Within those sections suggested format is: error message, explanatory context (often important -- a message that is very helpful in one context can be confusing in another), suggested improvements/changes.
    … …  
    2828== django.contrib.admin ==
    2929
    30 Ticket #1732 -- a problem that elicits no error message, but should.
    31 
    3230{{{
    3331'NoneType' object has no attribute 'get_field_sets'
    … …  
    3634'''Suggestion:''' Check relevant Admin settings during model validation?
    3735
     36 * Ticket #1732 -- a problem that elicits no error message, but should.
     37
    3838== django.core ==
    3939
    40 Ticket #1791 suggests better error messages in cases where application dependencies are not satisfied.
     40{{{
     41EnvironmentError: Could not import settings 'foo.settings' (Is it on sys.path? Does it have syntax errors?): No module named settings
     42}}}
     43'''Context:''' Application name is same as project name, causing import problems. (See #1908 for full example.)
     44'''Suggestion:''' Given how often beginners are likely to make this mistake, it would be nice for Django to look for this conflict and warn the user.[[BR]]
     45
     46 * Ticket #1791 suggests better error messages in cases where application dependencies are not satisfied.
    4147
    4248== django.template ==
    4349
    44 See [http://groups.google.com/group/django-developers/browse_thread/thread/42aff5c291a69041/d006eb5292b8aac3 this thread on the django-developers list] for discussion of error suppression in the template engine
     50 * See [http://groups.google.com/group/django-developers/browse_thread/thread/42aff5c291a69041/d006eb5292b8aac3 this thread on the django-developers list] for discussion of error suppression in the template engine
Back to Top