Re: No module named django after upgrade to os x Lion

Thanks a million, Kurtis! I followed your advice and I no longer get
any errors when I run "python manage.py runserver". Hurray :) !

I'll probably give PostgreSQL a try once I've got the hang of python
and django a bit more, since you were all so positive about that.

My next problem is that the command python manage.py synchdb does not
create any tables, but I've started a new thread for that :)
http://groups.google.com/group/django-users/browse_thread/thread/eca94f905a6bea10

Thanks for all your help!
/Angelika

On Oct 28, 7:56 pm, Kurtis <kurtis.mull...@gmail.com> wrote:
> Okay, I think I've got the exact steps down needed to get this running
> right. If these are actually it, I'm not sure if I had any other
> prerequisites I can't think of at the moment, then it's a matter of
> copying and pasting 3 lines into your terminal. (Less than 5-10
> minutes total)
>
> 1. Install "Brew" (http://mxcl.github.com/homebrew/)
> 2. Use Brew to Install mysql-connector-c
> 3. Install MySQL-python
>
> Open up your terminal and follow these steps. If you are unsure of
> anything during the process, then feel free to read more information
> on what these are. Google is your friend here :)
>
> /usr/bin/ruby -e "$(curl -fsSLhttps://raw.github.com/gist/323731)"
> brew install mysql-connector-c
> sudo easy_install mysql-python
>
> Hopefully that works for you! Good luck.
>
> On Oct 28, 12:19 pm, creecode <creec...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Hello Angelika,
>
> > On Friday, October 28, 2011 2:13:20 AM UTC-7, angelika wrote:
>
> > creecode, I tried the commands you suggested first. No matter which
>
> > > version I switched to, it still said No module named django, which
> > > seems weird but there it is.
>
> > If your curious about where the old Django install may have gotten to you
> > could try on the command line...
>
> > sudo find -x / -name django -print
>
> > So I ran sudo easy_install django, just
>
> > > to see if it could be that easy. When the install was done, it seemed
> > > to work at first. I could run import django, no problem. I started the
> > > tutorial on djangoproject.com and got as far as setting up a db and
> > > running python manage.py runserver, before the dreaded
> > > "django.core.exceptions.ImproperlyConfigured: Error loading MySQLdb
> > > module: No module named MySQLdb" started showing up. God damn it.
>
> > If you are just doing local development for learning I think you can bypass
> > the database install, at least that is what the Django Quick Install docs
> > indicate.
>
> > At this point I thinking maybe I should just switch to using
>
> > > PostgreSQL instead, if that would solve the problem. What do you guys
> > > think?
>
> > You could give it a go but if you're just wanting to get through the
> > tutorial is does seem like overkill.  I've just tried installing Postgres
> > on Mac OS X for the first time and it wasn't smooth sailing by any means.  
> > Part of the issues were related to installing the Postgres server on an
> > older OS version and hardware.  I did install psycopg2 on recent hardware
> > with current Lion and a fair amount of hair pulling.  psycopg2 is a
> > connector so that Django, through Python, will be able to talk to a
> > Postgres server.  It does the same job that MySQLdb does for MySQL.
>
> > Toodle-loooooooooooooo.............
> > creecode

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.