On May 18, 5:30 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]> wrote:
> Indeed; I've been telling people interested in getting stuff into > Django that doing it as a standalone project first is probably the > best idea. I really like the constraints that places on how these > external projects are developed, and it helps stablize the internal > Django APIs that these projects use. This project is great, but one little thing that bugs me in general is that there doesn't seem to be any kind of standard module naming convention for writing third-party apps like this. For instance, django-values expects you to put it in django.contrib.values, which seems a bit ugly. I've seen others which expect you to just put the module in the root namespace (e.g. the django-registration app). Is there any way around this, or is it just something inherent to Python? Jason --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
