Received: by 10.101.39.7 with SMTP id r7mr419603anj.9.1337122647136;
        Tue, 15 May 2012 15:57:27 -0700 (PDT)
X-BeenThere: pylons-devel@googlegroups.com
Received: by 10.236.113.208 with SMTP id a56ls74487yhh.8.gmail; Tue, 15 May
 2012 15:57:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.236.145.199 with SMTP id p47mr110762yhj.1.1337122645871; Tue,
 15 May 2012 15:57:25 -0700 (PDT)
Authentication-Results: ls.google.com; spf=pass (google.com: domain of
 jonat...@findmeon.com designates internal as permitted sender)
 smtp.mail=jonat...@findmeon.com; dkim=pass
 header...@findmeon.com
Received: by h10g2000yqn.googlegroups.com with HTTP; Tue, 15 May 2012 15:57:25
 -0700 (PDT)
Date: Tue, 15 May 2012 15:57:25 -0700 (PDT)
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8)
 AppleWebKit/534.55.3 (KHTML, like Gecko) Version/5.1.5 Safari/534.55.3,gzip(gfe)
Message-ID: <3104a16c-3e60-4efd-a725-479439b29b38@h10g2000yqn.googlegroups.com>
Subject: Documentation Suggestions for Subscribers or Debug
From: Jonathan Vanasco <jonat...@findmeon.com>
To: pylons-devel <pylons-devel@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1

I ran into an issue a few months ago regarding a NewResponse
subscriber and failing to catch errors (
https://groups.google.com/group/pylons-discuss/browse_thread/thread/54b5b3eb5e2ccfe/4e9a2abc09b9651f
)

As I prepare for a production release , my old code ( which i forgot
to remove ) started firing -- and I finally figured out what was
happening.

Because I had debugging turned on via 'development.ini', Pyramid was
catching the error & response object from the app, and replacing it
with its own.

In a perfect world, the Pyramid debug system would let the original
response/request stuff somehow persist -- so code can be written that
works on production and development.

In a less perfect, though perfectly acceptable world, it would be
great if the debug & event subscriber docs cross-referenced one
another with an alert/note box that simply states that the debug
system will 'overtake' the response object when turned on, and
subscribers that are designed to handle errors may not work as desired