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. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
