Its worse. If the memcache lines are commented out and the alternative line 
to connect and put tickets and sessions in the database, it still fails 
with both GAE SDK and production, this time with error

ProtocolBufferEncodeError: int64 too big

when executing 

session.connect(request, response, db=db)

So 2.9.3 wont work with GAE at all!

On Monday, March 3, 2014 5:01:34 PM UTC-5, Sebastian Cambeo wrote:
>
> This error persists in the current stable version 2.9.3:
>
> If you want to reproduce it just take the welcome app and uncomment the 
> three memcache session lines:
>
> from gluon.contrib.memdb import MEMDB
> from google.appengine.api.memcache import Client
> session.connect(request, response, db = MEMDB(Client()))
>
>
> and the whole application will crash:
> TypeError: __call__() got an unexpected keyword argument 'unique_key'
>

-- 
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/groups/opt_out.

Reply via email to