Why do you need a shared project to house generic apps? Why not just
put them at dango_root (or anywhere on your python path), and install
them in your django projects (sites)?
django_root/
genericapp1/
genericapp2/
mysite/
__init__.py
apps/
__init__.py
siteapp1/
siteapp2/
manage.py
settings.py
urls.py
I also put default templates with the apps, and override them with
project templates if need be.
If you work with several django sites, it may be desirable to have
each use their own private copies of django and generic apps, so that
individual sites can be upgraded without worrying about backwards
incompatible changes in django or generic apps. I do this with
Subversion externals.
trunk/
django/
genericapp1/
genericapp2/
mysite/
django/ (X)
genericapp1/ (X)
genericapp2/ (X)
mysite/
__init__.py
apps/
__init__.py
siteapp1/
siteapp2/
manage.py
settings.py
urls.py
All you need to do is set the python path to root/mysite/ for your dev/
production server or interactive shell. I do that with shell aliases/
scripts. Then you can still work on your generic apps within mysite,
and commit those changes directly back to the trunk version to be
utilised by other projects that track trunk, or new projects.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" 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-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
