You should use pip and virtualenv to create a sane development environment.
This guide [1] is originally aimed at ubuntu/linux, but I think you can probably follow in mac os x as well. I've also listed a few other links with instructions that look alright, but that I haven't tested. Basically, don't "ln -s". Use virtualenv instead. Quote from one of the links: *"On my systems, virtualenv, virtualenvwrapper, and Mercurial are the only Python packages that are always available — every other package is confined to its virtual environment."* While you might prefer something other than mercurial, the point still stands. Add only the bare minimum to the system-wide install and everything else to virtualenvs instead. Cheers, AT [1] http://www.saltycrane.com/blog/2009/05/notes-using-pip-and-virtualenv-django/ http://www.arthurkoziel.com/2008/10/22/working-virtualenv/ http://hackercodex.com/2011/08/30/python-install-django-on-mac-osx-lion-10.7/ http://www.djangoapp.com/blog/2011/07/25/django-installation-on-mac-os-x-lion/ On Wed, Mar 7, 2012 at 2:31 PM, Clark Corey <[email protected]> wrote: > I am typing mine into a shell prompt....I posted the thread, but I don't > know that it has posted yet...here it is: > > After installing Django I am attempting to start a new project. After > creating a directory for this, I tried using the command: "django- > admin.py startproject mysite". > > but I'm getting the message "-bash: django-admin.py: command not found". > > So, I've tried running this: > > "sudo ln -s library/python/2.6/site-packages/django/bin/django-admin.py > /usr/local/bin/django-admin.py" in which i get "file exists" > and I still get the same problem when running the startproject. > > Only other piece of info is that during installation I had a "error: > /usr/local/bin/django-admin.py: No such file or directory". But I can > cd into that directory and see the django-admin.py file. > > Thanks! > > -Clark > > > > On Wed, Mar 7, 2012 at 7:54 AM, Tom Evans <[email protected]>wrote: > >> On Wed, Mar 7, 2012 at 2:43 PM, Clark <[email protected]> wrote: >> > I am having a similar issue, so I tried the $ pip uninstall django, >> > but I got a "IOError: [Errno 13] Permission denied" >> > >> > Advice? >> > >> > Thanks. >> > >> >> You should have started a new thread for your new error. The error >> here was that the new user was typing shell commands into a python >> prompt - is that what you are doing? >> >> The error that you have shown means that pip tried to access (read or >> delete) a file to which it did not have access. That could happen for >> any number of reasons, but most likely you installed django as root >> and are trying to uninstall it as a regular user. >> >> Of course, that is just speculation, as you have not shown what >> happened, or what your original error was that made you think "I know, >> a reinstall of Django will fix everything". >> >> Cheers >> >> Tom >> >> -- >> 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?hl=en. >> >> > -- > 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?hl=en. > -- 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?hl=en.
