Julio is right that you can use the same app in multiple Django projects from the same common path. The key point here is that each Django project runs in a separate Python runtime environment. This is what makes this possible.
If you really meant using two instances of an app in the _same_ Django project, I think that Django will simple ignore the second appearance of that app in your settings.INSTALLED_APPS i.e. Django won't create two differently named sets of model tables for this app. However, if the app's model supports multiple blogs, you only need one instance of the app to make it handle as many blogs as you need in your single project. You would filter for your two blogs and their related entries using appropriate QuerySets. If the app works off of static settings/parameters that you need to set before you can use it, then you will have problems sending two different sets of parameters to it in the same Python runtime i.e. same Django project. But if the multiple blog support is fully DB driven, you should've no problems. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
