{"id":75188,"date":"2020-01-18T12:24:53","date_gmt":"2020-01-18T06:54:53","guid":{"rendered":"https:\/\/www.vskills.in\/certification\/tutorial\/?p=75188"},"modified":"2024-04-12T14:17:11","modified_gmt":"2024-04-12T08:47:11","slug":"djangos-pretty-error-pages","status":"publish","type":"page","link":"https:\/\/www.vskills.in\/certification\/tutorial\/djangos-pretty-error-pages\/","title":{"rendered":"Django\u2019s Pretty Error Pages"},"content":{"rendered":"

Take a moment to admire the fine web application we\u2019ve made so far \u2013 now let\u2019s break it! Let\u2019s deliberately introduce a Python error into our views.py file by commenting out the offset = int(offset) lines in the hours_ahead view:<\/p>\n

def hours_ahead(request, offset):<\/p>\n

# try:<\/p>\n

#     offset = int(offset)<\/p>\n

# except ValueError:<\/p>\n

#     raise Http404()<\/p>\n

dt = datetime.datetime.now() + datetime.timedelta(hours=offset)<\/p>\n

html = “<html><body>In %s hour(s), it will be  %s.<\/body><\/html>” %<\/p>\n

(offset, dt)<\/p>\n

return HttpResponse(html)<\/p>\n

Load up the development server and navigate to \/time\/plus\/3\/. You\u2019ll see an error page with a significant amount of information, including a TypeError message displayed at the very top: \u201cunsupported type for timedelta hours component: str\u201d<\/p>\n

\"\"<\/p>\n

What happened? Well, the datetime.timedelta function expects the hours parameter to be an integer, and we commented out the bit of code that converted offset to an integer. That caused datetime.timedelta to raise the TypeError. It\u2019s the typical kind of small bug that every programmer runs into at some point.<\/p>\n

The point of this example was to demonstrate Django\u2019s error pages. Take some time to explore the error page and get to know the various bits of information it gives you. Here are some things to notice:<\/p>\n