On Oct 23, 3:30 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > It's documented that way because it means we can have a tutorial that > doesn't immediately dump import-path configuration issues onto people > who are brand-new to Python; doing things the way the tutorial does > them, everything automatically ends up on the Python path thanks to > manage.py.
Things work just as magically with the dev server for apps inside the project dir if you simply import by the app name and omit the project name. manage.py puts both the project dir itself and its parent dir onto the Python path. So AFAICT, this particular reasoning is baseless. Carl --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
