Many app engine users are using their own django, uploaded with their app. Many of those people are also using the InstallAppengineHelperForDjango() also to make it work.
Possibly related. Many people including myself have been experiencing 500 errors that show class DeadlineExceededError in them. It usually occurs for most of us in the django or django helper code before our views or 'our code' even runs, before any datastore activity happens. So my questions are: 1. How does the import cache work exactly? I have read docs but still am left with questions on how exactly it works. If we have a main.py with our main() method in it... are all the imports in that file cached? Is there a way to keep our custom django in memory? 2. Since so many people use custom django, is there any plan to provide other versions of django besides the .96 version? Would it be possibe to provide .97 and 1.0 under some other name (import django97 as django)? I have read that the provided django is always loaded in memory and thus would be faster. It would sure save us a lot of files to upload also. 3. Do you have any other advice on using custom django? any advice on the high cpu warnings I get because of (IMO lgiht) datastore usage? (when the pay service is running, will that be less of an issue?) Thanks GAE team! -Mike --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
