Interestingly, the following code does seem to trigger overwrites of the
session file (though not consistently):
temp = BEAUTIFY(session)
Not sure what's going on there.
Anthony
On Monday, March 14, 2016 at 7:42:53 PM UTC-4, Anthony wrote:
>
> I'm on Windows with the same web2py and Python versions.
>
> On Monday, March 14, 2016 at 7:00:16 PM UTC-4, Alex wrote:
>>
>> I don't think a test app is that simple to create. It needs a db,
>> auth_user table, user entry with memberships, login form ... because the
>> issue only occurs if you're logged in.
>>
>
> Just start with the welcome app -- it has everything you need. Just
> register a single user and log in.
>
>
>> It is true that the pickled sessions are different after iterating the
>> user_groups as confirmed by Anthony.
>>
>
> Yes, but it appears that the pickling itself (in your code) leads to that
> issue. The real question, though, is whether the session file is
> overwritten on each request, and if you just iterate over auth.user_groups
> (with no pickling code), it does not appear that the session file is in
> fact overwritten.
>
> So, start with a fresh copy of the welcome app, register a user, log in,
> and add some code to iterate over auth.user_groups. Then observe directly
> the mtime of the session file and see if it changes with each request. If
> so, pack the application and post it here.
>
> Anthony
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
