On Monday, 7 December 2015 21:14:45 UTC, Caique Reinhold wrote: > > Well, as this is implemented you have to know your namespaces during > development. But now i see what's your problem. > > I'm not sure, but i don't think it is encouraged to have multiple > instances of the same app in one project. I think the sites > <https://docs.djangoproject.com/en/1.9/ref/contrib/sites/>contrib app or > some other method of having this author/publisher distinction within the > same app would better suit your needs. >
I don't have any needs (the author/publisher thing is from the Django docs, not my app), I'm just trying to write an utterly simple app and I'm trying to find out the "best practices" way of doing it. The impression I'm getting is that the documentation is misleading and the "instance namespace" feature does not actually really work. And that the answer to my question is that I should use an app namespace and put as part of the installation instructions for my app that the user must put app_name="foo" in their site's urls.py or the app will fail. I guess this is why one of the changes in 1.9 is that now you can define the app_name in the app rather than in the site. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/03e579b4-7a69-419f-9f41-1ba13203ed2e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
