On Dec 19, 4:26 am, Waldemar Kornewald <wkornew...@gmail.com> wrote: > There's nothing magic about the workarounds. In app-engine-patch > there's a sample project which gets you started immediately with the > latest stable release. Everything that's need is placed in a folder > called "common" and in order to upgrade you simply overwrite the old > files with the new ones in the latest sample project. Done.
Like I said, it's been hard enough getting up and going with just GAE. Every additional piece is more configurations, more documentation, more forums, more possible bugs, more possible constraints, etc. It looks like the app-engine-patch developers (you?) did a good job bringing newer Django to GAE, and that is respectable. All I am saying is that I'm not ready to deal with it. If I had ANY previous Django experience, that would be another story. > Webapp is no match for Django unless all you want to do is a simple > just-for-fun application. Well this gets into a philosophical debate... Some great desktop and console applications are written in assembly language, and that does not reflect poorly on C or C++. Not every large scale web app requires i18n, sessions, pluggable auth, etc. Don't take my thoughts as criticism of app-engine-patch or Django -- we all must learn and use the tools that are appropriate for the job at hand. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
