That's a valuable info. To me it seemed some Django-standard and those things are supposed to be well thought through, therefore we also broke our heads over it a couple times ... Thanks for the info.
Wolfram On 7/25/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > On 7/24/07, Sebastian Macias <[EMAIL PROTECTED]> wrote: > > My dilemma is... what is the point of having projects and apps if the > > applications created for my project won't be portable in other > > projects (becase the namespaces will always start with the project > > name). I can't just copy and app from one project to another. > > Personally I never use "projects" -- they were just a quick thing we > made up just before we open-sourced Django, with the thinking being > "projects" would make it quicker and easier for people to get started. > They are *not* a good method to use if you want to distribute your > application, however. > > We need better documentation about best practices to make apps portable. > > Adrian > > -- > Adrian Holovaty > holovaty.com | djangoproject.com > > > > -- cu Wolfram --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
