Well, you have to hope that behavior under the development server gives you a clue where to put the prints, or breakpoints. You might find yourself patching a piece of middleware to look for the troublesome path and only doing a set_trace() for it. Then you can single step your way into the url decoding code (another place to potentially put the set_trace() for your case) until you are surprised by the result.
Note that since this involves patching django itself, you may want to do this in a virtualenv. On Thu, Sep 16, 2010 at 11:58 AM, dclaar <douggoo...@claar.org> wrote: > Actually, DEBUG *is* on in the production instance. And yet, all I get > is the "No Testbeds match..." message, which was a bit surprising to > me. Without DEBUG, I just get a 404 not found. I'll try the clone > idea. The problem I have is: Where do I put the print statements? The > admin stuff is automagically generated from admin.py and models.py, so > I don't know where to hook. > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-us...@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
