I'm not familiar with the plugin, but I would guess that it's trying to add itself to the python path. That way it's easily available for any django project without having to include it in an individual project.
I would bet that it'd work just fine included manually in your project without running the install script. But again, it depends on the plugin. On Sep 25, 10:59 am, dijxtra <nsko...@gmail.com> wrote: > Hi everybody, > > Django applications, as I understood them should be pluginable on > project basis. That is, I should be able to install them to my > *project*, not to my django installation. So I downloaded django- > tagging and run the python setup.py install. And it failed: > n...@rilmir:~/code/my_project/django-tagging-0.3$ python setup.py > install > [...] > creating /usr/local/lib/python2.6/dist-packages/tagging > error: could not create '/usr/local/lib/python2.6/dist-packages/ > tagging': Permission denied > > Now, why is django-tagging trying to mess with my python directory? > Does that mean that when I commit my project to my repository and > checkout it on a different django installation django-tagging won't > work untill I install django-tagging on that machine? I thought that > when I install an django app, then I install it in my project and my > project is still portable. But, if django-tagging is putting files in > directories outside my project directory, doesn't that make my project > un-portable? > > Could someone please clear this up for me? > > Thanks, > nick. --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
