If the response is left off the session.forget() parameter list it defaults 
to None. The end result then is the session._forget state variable is set 
True but the session file is not unlocked in the _unlock function. This 
would enhance performance by bypassing the writing of the session file at 
the end of the request-response cycle when the session state is unchanged 
but won't release the lock to let other requests proceed on that session. I 
could see this as a possible use of session.forget(..) so it looks like a 
documentation issue.

Reply via email to