diff options
| author | Justin Bronn <jbronn@gmail.com> | 2007-10-26 20:47:20 +0000 |
|---|---|---|
| committer | Justin Bronn <jbronn@gmail.com> | 2007-10-26 20:47:20 +0000 |
| commit | 4ffbddf92d89c3b31cef90043721184a501cd454 (patch) | |
| tree | db8131d40b0a5437270a6b1e8d579113ab3508e8 /docs/databases.txt | |
| parent | f66ee9d0065838a0f6c9c76203a775a78446cdf7 (diff) | |
gis: Merged revisions 6525-6613 via svnmerge from [repos:django/trunk trunk].
git-svn-id: http://code.djangoproject.com/svn/django/branches/gis@6615 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/databases.txt')
| -rw-r--r-- | docs/databases.txt | 8 |
1 files changed, 8 insertions, 0 deletions
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 |