diff options
| author | Casey Duncan <casey.duncan@gmail.com> | 2010-12-12 10:36:13 -0700 |
|---|---|---|
| committer | Casey Duncan <casey.duncan@gmail.com> | 2010-12-12 10:36:13 -0700 |
| commit | e667ef0c1e442aaa22553ec9dee6fb7e827036f9 (patch) | |
| tree | e19fcbb13e8ae71e681acd5063e52a7704b7a420 | |
| parent | 729fd3f16ab77c7c56c73d0a79406473cd7b8b80 (diff) | |
| download | pyramid-e667ef0c1e442aaa22553ec9dee6fb7e827036f9.tar.gz pyramid-e667ef0c1e442aaa22553ec9dee6fb7e827036f9.tar.bz2 pyramid-e667ef0c1e442aaa22553ec9dee6fb7e827036f9.zip | |
clarify paragraph about when to call ISession.changed, uh huh, yeah
| -rw-r--r-- | docs/narr/sessions.rst | 5 |
1 files 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 |