On Apr 27, 2008, at 9:06 PM, Jonathan Vanasco wrote:

in a semi-related Beaker issue, i learned the other day that beaker
will throw a fatal pylons error if a class definition changes - or is
removed - from an existing session that is reloaded.

this is because Beaker only checks for one type of exception in the
try/except block when it unserializes/unpickles the session data.

What's the other exception that is occurring?

- Ben

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to