Hi Oliver, The copy of Django included in the SDK is unmodified. If you need the modifications made by app-engine-patch, it's up to you to include them (or up to them to support included Django instead of zipimported one).
-Nick Johnson On Thu, Jun 25, 2009 at 12:19 AM, Oliver Zheng <[email protected]>wrote: > > I am currently using app-engine-patch, but now that Django 1.0 has > been released on GAE, I'd like to port my app over. App-engine-patch > zipimports Django and patches a lot of things to make it work out of > the box, for example the User model is modified to use GAE models, and > memcache is used for sessions. > > How does the Django lib on GAE provide this functionality? What > happens when I invoke 'request.user'? The SDK just uses my local > installation of Django, which is obviously unpatched. IIRC, app-engine- > patch creates a session model and stores user sessions in the > datastore and caches each session in memcache. 'request.user' pulls > the session and the user from either memcache or datastore if the > cache is purged. > > I can only think of this issue when porting my app to the Django > provided by GAE. Anything else I should be aware of? > > > -- Nick Johnson, App Engine Developer Programs Engineer Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
