Yes.
I'll file file a github issue.
Thanks.
On Tue, Oct 11, 2016 at 5:39 PM Anthony wrote:
> And just to clarify, that test passes if you remove the
> session.forget(response) line?
>
> If so, could be a webclient.py bug -- please file a Github issue.
>
>
> Anthony
>
>
> On Monday, October 10, 2
And just to clarify, that test passes if you remove the
session.forget(response) line?
If so, could be a webclient.py bug -- please file a Github issue.
Anthony
On Monday, October 10, 2016 at 3:54:54 PM UTC-4, Mathieu Clabaut wrote:
>
> Hello Antony,
>
> The simplest failing test I run is the o
Hello Antony,
The simplest failing test I run is the one from gluon/tests/test_web.py in
TestWeb.testRegisterAndLogin from commit
e6a3081b42ecd58441419930266baf286561c4c7.
Where the default controller has only a line added to forget session and
reads :
def index():
session.forget(response)
> I think the problem lies in `gluon/contrib/webclient.py` as the test works
> well when using another browser like firefox.
> I just tried to call another action without `session.forget` before
> calling `index`, but the test still failed after registration.
>
Looking at the webclient.py code
Thank you Anthony for asserting that the session is not cleared.
I think the problem lies in `gluon/contrib/webclient.py` as the test works
well when using another browser like firefox.
I just tried to call another action without `session.forget` before calling
`index`, but the test still failed a
session.forget() does not clear the session or stop the cookie from being
exchanged -- it just prevents any changes in the session from being written
to the persistent session storage.
I'm not sure, but maybe your webclient test doesn't work because the test
first calls /index and then immediat
6 matches
Mail list logo
