What steps will reproduce the problem?
1. Try to learn Python, Django and App Engine at the same time
2. Find that Django tutorial mentions things that don't exist anymore
3. Get confused
What is the expected output? What do you see instead?
Found no other way to contact you, so I just wanted to mention this here: I
think it gets very confusing that AppEnginePatch uses a lot of different
conventions from the things mentioned in the Django tutorial. For example,
it seems to introduce a completely new url handling pattern ("Automatic app
urls integration") - according to the tutorial, there should be an
"ROOT_URLCONF" in settings.py which doesn't even exist anymore.
I can understand if you want to solve some shortcomings of Django (like app
modularity), but why don't you do that in an AddOn to Django? My motivation
to use Django on App Engine is to not be too tied to App Engine. But if App
Engine Patch changes all of the conventions, that motivation is lost,
because I gets harder and harder to move away from App Engine. I think it
would be better to concentrate on just making "standard Django" work on App
Engine, and provide an optional Add On for all the stuff that irks you,
which could then be used on both standalon Django and App Engine Django.
The "sample app" approach also makes it very difficult to arrive at some
clean implementation of a simple app. Personally I would prefer to start
from very little and only add what I need, rather than trying to figure out
which of the countless settings are even relevant to my app. My feeling is
that ragendja should probably be extracted from the project...
What version of the product are you using? On what operating system?
AppEnginePatch1.1RC
Please provide any additional information below.
Original issue reported on code.google.com by Bjoer...@googlemail.com on 1 Nov 2009 at 9:21
Original issue reported on code.google.com by
Bjoer...@googlemail.comon 1 Nov 2009 at 9:21