Debug page traceback should highlight local code vs. framework code

[Thomas Güttler <hv@…>]

The debug traceback is very good.

But if the stacktrace
has many lines, it is hard to find your code.

Here is a simple patch, which guesses if the filename
is my code or djang/python code. If it is my code,
display the filename bold.

Since django and python code have no errors (simley),
I can see the buggy file quicker.

[Thomas Güttler <hv@…>]

Better patch.

[Adrian Holovaty]

I like this idea a lot, but the patch uses a hackish way to determine which code is Django vs. your own code. Could this be improved? Also, the design should be improved -- we should get Wilson's thoughts on this.

[Kevin McConnell]

Show bold filenames where file in INSTALLED_APPS

[Kevin McConnell]

The attachment views_debug_py.3.diff has a different way of deciding whether a file is "application code" vs. code from Django (and other libs, etc). It gets the load path for each item in INSTALLED_APPS (excluding django.* items), and considers a file to be application code if it falls under one of those paths.

I discussed this with Malcolm during the sprint and he felt this was a reasonable approach. (After all, once you get outside the INSTALLED_APPS directories, it's pretty hard to decide what else to count as part of the application.)

Matching filenames are shown in bold.

[Thomas Güttler]

thank you kevin for imporving my patch. I took your solution and changed only a bit:

• If the application model is defined in app/models/ instead of app/models.py, an other dirname() call is needed.
• Bold line number and code line

[(none)]

Milestone post-1.0 deleted

[Thomas Güttler]

#11834 has a more simple way to check for django vs. application code.