I fear you have to do a decision either the comfortable Django framework or zero quota.
After deletion of registration, admin and so on there may remain the automatic session management, the automatic handling of zip packages (Django alone are several hundred files) and more. As already described in Python Group http://groups.google.de/group/google-appengine-python/msg/43a4cd730772c7ae?hl=en AppenginePatch is coming with a sample installation you can code simply by using parts of the sample. http://code.google.com/p/app-engine-patch/ The sample contains working registration with email activation, session management, auth, administration, flatpages, remote access, automatic zip package handling, an itelligent profiler, and more out of the box. Naturally this is achieved by using some resources. If you want to stop this usage you have to unregister (comment out) the corresponding modules (especially 'myapp') in the 'Installed Apps' block of the settings file as explained in the 'Introduction' of the manual: http://code.google.com/p/app-engine-patch/wiki/GettingStarted Where it reads: For production use you should remove myapp and all its references in the base.html and main.html templates because it contains a view which allows for resetting the admin user ( so that you can test Django administration after download immediately). If you have got further questions you should post to the AppenginePatchGroup http://groups.google.de/group/app-engine-patch?hl=en --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
