From c858efe912603a0fc0d391bfcf0354f784071ad1 Mon Sep 17 00:00:00 2001 From: Malcolm Tredinnick Date: Sat, 20 Oct 2007 10:47:57 +0000 Subject: [PATCH] Fixed #5512 -- Added a note about a common MySQLdb upgrade problem. Thanks, Matt Boersma. git-svn-id: http://code.djangoproject.com/svn/django/trunk@6561 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/databases.txt | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/databases.txt b/docs/databases.txt index 213c2d666c..4530a1b896 100644 --- a/docs/databases.txt +++ b/docs/databases.txt @@ -76,6 +76,14 @@ the ``mysql`` backend. If you are trying to use an older version of MySQL and the ``mysql_old`` backend, then 1.2.0 *might* work for you. +.. note:: + If you see ``ImportError: cannot import name ImmutableSet`` when trying to + use Django, your MySQLdb installation may contain an outdated ``sets.py`` + file that conflicts with the built-in module of the same name from Python + 2.4 and later. To fix this, verify that you have installed MySQLdb version + 1.2.1p2 or newer, then delete the ``sets.py`` file in the MySQLdb + directory that was left by an earlier version. + .. _MySQLdb: http://sourceforge.net/projects/mysql-python Creating your database