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 c
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 "Bre
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 inst
Alright, I'm gonna give PostgreSQL a try over the weekend, I'll let
you know how it works out.
Thanks, guys!
/Angelika
On Oct 28, 12:49 pm, Kurtis Mullins wrote:
> I'd give PostgreSQL a shot and see if it magically works for you. It's an
> awesome database. If you have any problems with it though
I'd give PostgreSQL a shot and see if it magically works for you. It's an
awesome database. If you have any problems with it though, here's the "easy
way out" I took. I just installed Mac Ports and never had another problem.
Of course, you'll have to make sure you're using the Mac Ports tools you
i
PostgreSQL is great, you will have no regrets!
Cheers,
AT
On Fri, Oct 28, 2011 at 6:13 AM, angelika wrote:
> Thank you all for your help and suggestions. Last time I installed
> Django it took a full two days and I was nearly in tears at the end.
> Most of the time was spend trying to solve th
Thank you all for your help and suggestions. Last time I installed
Django it took a full two days and I was nearly in tears at the end.
Most of the time was spend trying to solve the problems that Kurtis is
talking about, with the MySQLdb package. Although I am usually not a
person who takes shortc
IMHO, If you can't understand how imports and sys.path work, it's best to
put the Django book aside and read up on the basics of installing and
running Python.
Cheers,
AT
On Thu, Oct 27, 2011 at 1:55 PM, creecode wrote:
> Angelika may not want to get into virtualenv and virtualenvwrapper at th
Angelika may not want to get into virtualenv and virtualenvwrapper at this
point. If you're just getting into Python/Django it may be more overhead
than you want to deal with conceptually at this time. If your project is
simple or you're just learning then you may want to wait until you feel t
Hello Angelika,
As a test you may want to try the defaults command ( for more info "$ man
defaults" and/or google "mac os x defaults" ) to see if your Django install
is still in the site-packages of an older version of python. Try something
like this on the command line...
$ defaults write co
Mac OS has always carried multiple Python installs. You can start
python using python2.5, python2.6, and on Lion python2.7. Those
installs are under /System/Library/Frameworks/Python.framework/ but
links to the executables are in /usr/bin/.
When you install Python packages, they get installed in /
On Thu, Oct 27, 2011 at 9:20 AM, Kurtis Mullins
wrote:
> If you don't want to use the complexity of the virtual environment, just run
> "sudo easy_install django" or "sudo pip install django" from your terminal.
> This will install Django system-wide.
the same commands work inside a virtualenv. w
Good luck with installing MySQL-python. You'll probably see an error at some
point that the Module MySQLdb is missing if you use MySQL and don't install
it. Last time, with Snow Leapord, I had to install "Mac Ports" to get it
working.
If you don't want to use the complexity of the virtual environm
On Thu, Oct 27, 2011 at 2:43 PM, Andre Terra wrote:
> You can run different versions of python using virtualenv [1]. It is hands
> down the best way to handle multiple python environments.
>
> You can use virtualenvwrapper [2] to automate some of the process. I'm not
> sure how good it is on Mac O
You can run different versions of python using virtualenv [1]. It is hands
down the best way to handle multiple python environments.
You can use virtualenvwrapper [2] to automate some of the process. I'm not
sure how good it is on Mac OS, but you should be fine. I found a link [3]
that looks like
Thanks, Tom. I see. So basically I need to reinstall Django, if I want
to run it on Python 2.7.1, is that it?
As far as I can tell, the older versions of Python are still installed
on my machine. Does that mean that it might be possible to run an
older version instead, and not have to reinstall Dj
On Thu, Oct 27, 2011 at 7:17 AM, angelika wrote:
> Hello,
>
> I'm new to both Python and Django. A few months ago, I installed
> Django on my mac (running Snow Leopard). I took me quite some time,
> but I got it running. After that I didn't get around to doing anything
> with it. A few weeks ago,
Hello,
I'm new to both Python and Django. A few months ago, I installed
Django on my mac (running Snow Leopard). I took me quite some time,
but I got it running. After that I didn't get around to doing anything
with it. A few weeks ago, I upgraded my mac to run Lion and now, when
I type import dja
18 matches
Mail list logo
