Welcome !
On Jul 30, 2:01 pm, "Peter Melvyn" <[EMAIL PROTECTED]> wrote:
> On 7/30/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
> > Try {% debug %}
>
> If you mentioned this feature: is there an easy way to reformat {%
> debug %} output the same/similiar way an exception error is reported?
look at the <head> content of debug pages and copy/paste anything you
find usefull (css, js). You may wrap you debug thing inside a div and
make easier to use with some javascript love :). You may also write
some middleware (?) to include automatically this things in your pages
when debug is on, and release to the community (yeah!)
I don't how complex is your application but most of the time you don't
need to dive into variables that way at least I never did this with my
own application in python/django. Most of the time I use directly
Model Instance or for complex views I prepare some variables in the
view.py file so that it's easier to build (more readable) pages.
Don't forget the python/ipython shell it should be your fellow friend
when writing any python bits because it helps a lot: learn,
experiment, build... more that with any print crap :).
-- Amirouche
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
