On 2/14/07, Frank Tegtmeyer <[EMAIL PROTECTED]> wrote: > except that there is no central registry for application names, right? > So one could have two applications called "payment" where one would be > for credit cards, the other for anonymous payment. What if he needs > both and they are made by someone else? > Ok, not very likely. But possible.
It's possible, but it's always *possible* to generate a namespace conflict if you try hard enough (though Django does do a little bit for that by telling you not to use 'site' or 'test' as project names), and there will always be edge cases where you'll need to rename a directory to avoid a clash. But in general, distributing templates with an application and using the 'app_directories' template loader makes reusable apps a lot easier, and since you'd already have to worry about name clashes (if you had two apps named "payment", it wouldn't just affect templates -- it'd affect any code you tried to import from one of them), don't let it bug you too much ;) -- "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 -~----------~----~----~----~------~----~------~--~---
