On Sun, Oct 19, 2008 at 1:55 AM, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > However, it's important to note that this doesn't preclude the use of > deeper namespaces - it just says that namespacing for an application > shouldn't be tied to the project. One obvious way to satisfy this > would be to create namespaces for the company, rather than the > project. For example, if you work for WhizCorp, create a > whizcorp.story application, and then create a whizcorp.foobar project > that imports whizcorp.story.
(this is the part where James points out that the slides from the "reusable Django apps" talks he's given include examples of doing this) -- "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 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 -~----------~----~----~----~------~----~------~--~---
