> I was now able to track down to code that triggers IIS to throw the unhandled > exception.
That's interesting, but please let's keep the information on the wiki bug page (noone will dig through the mailing list when trying to fix bugs). > r = copy.copy(request) <-- IIS exception is caused Oops, that's strange. > Exception RuntimeError: 'maximum recursion depth exceeded while calling a > Python object' in <type 'exceptions.AttributeError'> ignored If you just see that in the log, without the usual traceback, it likely means that there was a (rather simple) error handler that catched it and just logged minimal information. > Yet it seems that the standalone script handles the condition more gracefully > than if the code is executed as ISAPI application under the command of IIS. Well, or it does not happen at all there. Maybe the "request" object has something that causes issues with copy in one case, but not in the other? > There is also one more thing I cannot understand. When I run the standalone > script an exception is being reported yet I am not able to catch it. If there is a more "inner" error handler that catches it, your handler won't get it. > Apart from this mail I will also file a bugreport at > http://moinmo.in/MoinMoinBugs describing my setup and all the observations I > have already made. Great! :) ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Moin-user mailing list Moin-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/moin-user
