From yuri at sims.berkeley.edu Mon Aug 25 07:14:42 2008 From: yuri at sims.berkeley.edu (Yuri Takhteyev) Date: Mon Aug 25 07:26:59 2008 Subject: [Sputnik-list] error handling Message-ID: fa4efbc00808250214m2f7a394dyaee84f4bb9f7b21d@mail.gmail.com

In response to David's comments the other day, I reworked error handling. Sputnik now generates its own error message regardless of where the problem happens, even if sputnik.new() fails. If your logging is configured, the error will be logged as long as the logger is initialized successfully, which is now the first thing that we try to do. This is all achieved by moving all the error handling and reporting logic out of the Sputnik class. (I ended up putting it into a separate module: sputnik.wsapi_app.) If the application factory cannot initialize Sputnik, it just returns a dummy function that responds to each request with an error message. As I mentioned earlier, the stack traces are hidden by default but could be activated with a parameter:

See http://gitorious.org/projects/sputnik/repos/mainline/commits/b1489f63

I am wondering now whether to consider this a bug fix to "Earth" or as a the first feature for "Fenchurch".

I also changed the way sitemaps are displayed: you now only get to see in the sitemap those pages that you would be authorized to see the content of. You still don't see the default pages, though.

-- http://sputnik.freewisdom.org/