And thank you for the pointer to the modwsgi debugging page.
On Fri, Oct 1, 2010 at 12:39 PM, dclaar wrote:
> Just as a follow-up,
> http://code.google.com/p/modwsgi/wiki/DebuggingTechniques#Python_Interactive_Debugger
> was pretty helpful. In the end, it turned out to be one of those
> incredib
Just as a follow-up,
http://code.google.com/p/modwsgi/wiki/DebuggingTechniques#Python_Interactive_Debugger
was pretty helpful. In the end, it turned out to be one of those
incredibly frustrating Regular Expression things, where the fix was to
add a "^" anchor to a single RE.
Without an “^” anchor
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 d
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 automagi
I think that I'd start by making a clone, on some development box,
run using the development server, but with SUB_SITE='perf/'.
The removes the most glaring difference between your development
and production versions. If it fails there you have full recourse to
print statements and pdb.
That said
5 matches
Mail list logo
