Yes, this took care of it. Thanks.
I guess I should have read the documentation more carefully, since it
does say I needed to cd to myproject/apps before creating an app.
Just as a suggestion, however, it might be useful to mark visually
more clearly in the text the actual steps that the user need to do.
The tutorial has a lot of detailed background information, which is
very useful, but it is easy to miss a step among them. One possibily
is to include trivial commands like "cd" in green code blocks, saying
cd myproject/apps
in addition to "change into the myproject/apps directory", not because
the readers are not going to figure out how to change the directory
but because this could make it possible to use the green code blocks
as a check list of things you needed to have done by now.
Another possibility to consider is adding error messages for import
cases. Django seems to do a lot of magic with importing, which makes
hard for the user to figure out where exactly it expects to actually
find the modules. Perhaps it would help if the code that did the
importing magic printed a message saying what exactly it was looking
for ("myproject.apps.polls" in this case).
But that's all details - it's a great framework and a great tutorial.
- yuri
On 12/28/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> Hey Yuri,
>
> Move the "polls" directory into "myproject/apps", and give it another
> shot. You're trying to import myproject.apps.polls, but that directory
> doesn't exist. Good luck!
>
> Adrian
>
> --
> Adrian Holovaty
> holovaty.com | djangoproject.com | chicagocrime.org
>
