From e667ef0c1e442aaa22553ec9dee6fb7e827036f9 Mon Sep 17 00:00:00 2001 From: Casey Duncan Date: Sun, 12 Dec 2010 10:36:13 -0700 Subject: clarify paragraph about when to call ISession.changed, uh huh, yeah --- docs/narr/sessions.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/narr/sessions.rst b/docs/narr/sessions.rst index 8d057bdd1..a7fe9ab7d 100644 --- a/docs/narr/sessions.rst +++ b/docs/narr/sessions.rst @@ -123,8 +123,9 @@ Some gotchas: modify a session object directly, such as setting a value (i.e., ``__setitem__``), or removing a key (e.g., ``del`` or ``pop``), the session will automatically know that it needs to re-serialize its - data, thus calling ``changed()`` is unnecessary. When in doubt, call - ``changed()`` after you've changed sessioning data. + data, thus calling ``changed()`` is unnecessary. There is no harm in + calling ``changed()`` in either case, so when in doubt, call it after + you've changed sessioning data. .. index:: single: pyramid_beaker -- cgit v1.2.3