On Thu, Oct 23, 2008 at 1:47 PM, bruno desthuilliers <[EMAIL PROTECTED]> wrote: > It's indeed a pretty bad idea to refer to the project name in import > statements (as well as in a couple other places too FWIW), and I > defnitively fail to understand why it's documented that way.
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. This means, of course, that there is a need for followup documentation which explains that this isn't always the best way to develop real-world apps (in just the same way as the tutorial shows several "wrong" ways to do things like template rendering, etc., before showing the "right" way). Any volunteers to write it? -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
