Just started testing version 2.19.1 (prior to upgrading) with py3.6 and it appears that when sessions are stored in redis, a new session is being created each time the login is submitted which then prevents a session from logging in.
This issue was discussed in https://groups.google.com/forum/#!msg/web2py/z1ee025ghRU/qByNuEjGAgAJ and Jim S found a workaround with the .decode function which worked on py3 but not on py2 (and which I've been using live). It looks like the redis session code has been refactored in 2.19.1 to remove all the decodes but I can't get it to work correctly. Can anyone confirm whether they have this issue when trying to login using redis sessions in 2.19.1 (with py3)? If confirmed, I'll file a bug report. Thanks, Jose -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/37d39ee0-c7a8-4b42-a5f3-896d2e1cf847%40googlegroups.com.
