Adrian and hugo, thanks for the specifics. Seems like good material for a wiki page on "alternative" Django setups. If projects are just a convenience, and some of the biggest Django-powered sites aren't even using them, that is definitely worth covering explicitly.
I can imagine this might seem like a non-issue for core Django developers -- Django doesn't care, you can do anything you want, right? -- but as Adrian points out, even a default directory structure can seem like the One Way To Do It in the absence of specific alternatives. As for the "projects" name, I don't have a problem with it now that the distinctions have been clarified. thanks pb --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
