I just recently upgraded to Django v1.2.3. I'm really diggin' this new version so far. The framework has significantly matured now. There were no major problems with porting my existing sites except when I went into the CMS, would make an edit and then tried to save any changes to the db and I would get the following error message: "CSRF verification failed. Request aborted." I had NEVER seen that error before and no idea what to do. As with most things related to Django, (and really almost all open source projects), there was no documentation on this error. Not in the release notes. Not in the online documentation. Nowhere! I was foreseeing a long night ahead of me trying to get to the bottom of this error. So after some digging around I came across this blog entry from Jordan Messina that solved it for me. I sharing the solution here. Simply edit your settings.py file and add the following lines to the MIDDLEWARE_CLASSES section: 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.csrf.CsrfResponseMiddleware', So it should now look like this: MIDDLEWARE_CLASSES = ( 'django.middleware.common.CommonMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.csrf.CsrfResponseMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', ) Kill the server. (If it's running.) Run "syncdb". Run the server and voila... when you save all should be good with the world. This saved me hours of my life. (Your mileage may vary.)

At WebSight Design we try to remain technology-agnostic. (The right tool or language for the job.) Having said that, we are primarily a PHP shop. However, with the launch of the Google App Engine, we've been looking seriously at Python. In recent years, I have become a big fan of development frameworks so to aide me in learning the ways of the snake, I have been using the Django framework. Getting it all setup wasn't difficult. The Django installation is very easy. I started to get errors when I was trying to get my models working when I ran manage.py syncdb. Come to find out that I needed the MySQL-Python library installed to work correctly on my OSX Leopard machine. Most everything that I illustrate below is to be executed from the command-line. So if you are not familiar with working in the Terminal app, this post is gonna suck for you. So here is what I did to get it working: First, download MySQL for Python http://sourceforge.net/projects/mysql-python for me it was MySQL-python-1.2.2.tar Unpack it: tar -xzf MySQL-python-1.2.2.tar Change to the directory that is created: cd MySQL-python-1.2.2 Next, locate your "mysql_conf" file. locate mysql_conf Copy the location of this file so you can use it in the next few steps. Next, you need to edit the "site.cfg" file and add the path to your "mysql_conf" file. mysql_config = "YOUR_PATH_GOES_HERE" Also, (very important), change the line that reads: threadsafe = True TO threadsafe = False Save and exit the file. Now, compile and install the library: python setup.py build sudo python setup.py install NOTE: You may need to run "python setup.py clean" if you previously tried to build and install the library. Next is the *really* important part. After I kept getting errors trying to run the Python server I found the missing piece on the ProjectMouse.org site. The key is, you need to create a symbolic link in the location that Python is expecting to find MySQL. This should be a link to the MySQL library that your computer is setup to use. See here: sudo mkdir /usr/local/mysql/lib/mysql/ sudo ln -s /usr/local/mysql-5.0.41-osx10.4-i686/lib/libmysqlclient_r.15.dylib /usr/local/mysql/lib/mysql/libmysqlclient_r.15.dylib NOTE: "mysql-5.0.41-osx10.4-i686" is where MySQL is installed on my machine. Change this to the location specific to your computer. Finally, import MySQLdb into Python and test your configuration: python import MySQLdb NOTE: You should not see any errors or warnings. Hit "Ctrl+d" to exit the interepter. Now go back and run manage.py syncdb again and you should not get any errors.