Everyone,

THANKS!!! with your help i got everything working, also learned a lot
about the command line and how symbolic links and things residing in
the /usr/bin work.

I basically just had to remove all the links and some garbage that
macports left behind and relink everything like you guys said. Thanks!

back to learning django!



On May 14, 8:44 pm, Graham Dumpleton <[EMAIL PROTECTED]>
wrote:
> On May 15, 2:32 am, Jason Ourscene <[EMAIL PROTECTED]> wrote:
>
> > Ok now that the shock has passed a bit, anyone know how to do this
> > without reinstalling the OS.
>
> Do you still have the directory:
>
>   /System/Library/Frameworks/Python.framework
>
> and:
>
>   /Library/Python/2.5/site-packages
>
> present on your system?
>
> If you removed the first one as well, then a reinstall is necessary.
>
> If the first directory still exists, then go into /usr/bin and fix up
> all the python symlinks to look like:
>
> $ cd /usr/bin
> $ ls -las python*
> 8 lrwxr-xr-x  1 root  wheel  72 Nov 23 23:59 python -> ../../System/
> Library/Frameworks/Python.framework/Versions/2.5/bin/python
> 8 lrwxr-xr-x  1 root  wheel  79 Nov 23 23:59 python-config -> ../../
> System/Library/Frameworks/Python.framework/Versions/2.5/bin/python-
> config
> 8 lrwxr-xr-x  1 root  wheel  75 Nov 23 23:59 python2.5 -> ../../System/
> Library/Frameworks/Python.framework/Versions/2.5/bin/python2.5
> 8 lrwxr-xr-x  1 root  wheel  82 Nov 23 23:59 python2.5-config -> ../../
> System/Library/Frameworks/Python.framework/Versions/2.5/bin/python2.5-
> config
> 8 lrwxr-xr-x  1 root  wheel  73 Nov 23 23:59 pythonw -> ../../System/
> Library/Frameworks/Python.framework/Versions/2.5/bin/pythonw
> 8 lrwxr-xr-x  1 root  wheel  76 Nov 23 23:59 pythonw2.5 -> ../../
> System/Library/Frameworks/Python.framework/Versions/2.5/bin/pythonw2.5
>
> If the site-packages directory is missing, create it with permissions
> as below:
>
> $ ls -lasd /Library/Python/2.5/site-packages
> 0 drwxrwxr-x   65 root  admin  2210 Feb 13 15:33 /Library/Python/2.5/
> site-packages
>
> Please resist trying fink or MacPorts, just get your OS version
> working again. These third party packages can cause more grief than
> good at times. :-(
>
> Graham
>
> > Thanks!!!
>
> > On May 14, 11:47 am, Jason Ourscene <[EMAIL PROTECTED]> wrote:
>
> > > Looks like i deleted everything associated with python.
>
> > > On May 14, 10:55 am, Jason Ourscene <[EMAIL PROTECTED]> wrote:
>
> > > > I ran the command /usr/bin/python
> > > > and i get: No Such File or Directory.
>
> > > > This cant be good.
>
> > > > On May 14, 10:30 am, gordyt <[EMAIL PROTECTED]> wrote:
>
> > > > > Jason try this command and see if it works:
>
> > > > > /usr/bin/python
>
> > > > > If that takes you into the Python interpreter then you know that
> > > > > Apple's python is still OK.
>
> > > > > So your only problem is that you have the directory /opt/local/bin in
> > > > > your $PATH   ahead of the other directories that are normally in your
> > > > > path.
>
> > > > > The macports system automatically adds /opt/local/bin to your $PATH.
> > > > > Take a look here:
>
> > > > >http://guide.macports.org/#installing.shell
>
> > > > > In my case, I have these lines in my .bash_login file (located in my
> > > > > home directory):
>
> > > > > export PATH=/opt/local/bin:/opt/local/sbin:$PATH
> > > > > export MANPATH=/opt/local/share/man:$MANPATH
>
> > > > > These lines may be in any of the following files in your $HOME
> > > > > directory:
>
> > > > > .bash_login
> > > > > .bash_profile
> > > > > .profile
>
> > > > > Just edit them out, log out and back in, and your old $PATH should be
> > > > > restored to normal.
>
> > > > > --gordon
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to