Installing Django and MySQL on Mac OS X 10.7 from a fresh install.
( In point form, because I'm in a hurry. )

Windmill is a browser-integrated webapp testing system, similar to Selenium (if you've heard of that).

I tried to install it, but came up with this error:
ERROR: Cannot figure out interface name, please set NETWORK_INTERFACE_NAME in local settings file

( Here's how I solved my specific problem… )

From Strategies for Database Development And Deployment:

Pushing these changes to the production database at deploy-time is a one-click operation: open SQL Server Management Studio, connect to your production database, open a New Query window, paste the contents of the change log, and click Execute to run the script.

( One click, assuming you do all the other steps using keyboard shortcuts! )

I got this helpful error message:

psycopg2.DataError: value too long for type
character varying(50)

There was no traceback that was related to any of my code at all. Then I checked the PostgreSQL logs, and found this:

… [1818] user=alex,db=test_eve-online STATEMENT ( Read more... )

Sometimes when working through the Django shell (really just the Python shell, with Django libraries preloaded), I'll find I need to make a change to a model. At this point, I need to reload the model so I can continue using it through the shell.

Simply reload the model into the shell:

import people.models ( Read more... )

Rama Vadakattu wrote up a list of 10 tips for new Django developers. Worth reading!

( I've been having weird and wonderful problems with Python decorators of late. )

Here's a situation: you're writing a test suite for a web application, and you notice that - as an example - one of your models has a bunch of checkboxes. These checkboxes are used as "reminders" for various types of thing that the model is working with. Each type of thing has a number of checkboxes that it might use, but at this point in time all ( Read more... )

Okay, so this isn't really MySQL's fault. It's a Django problem. Way back in the day this application that I'm maintaining was written in Django 0.95. I've managed to port the forms and models across to Django 1.0-ish. I've included South so we can do database schema migration (and in fact part of the first batch of fixes was to improve performance ( Read more... )

Someone else mentioning virtualenv as a means of helping maintain production systems running under Django: A Django Development Environment with zc.buildout.