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
This commit is contained in:
parent
233d76cf25
commit
c858efe912
|
@ -76,6 +76,14 @@ the ``mysql`` backend.
|
||||||
If you are trying to use an older version of MySQL and the ``mysql_old``
|
If you are trying to use an older version of MySQL and the ``mysql_old``
|
||||||
backend, then 1.2.0 *might* work for you.
|
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
|
.. _MySQLdb: http://sourceforge.net/projects/mysql-python
|
||||||
|
|
||||||
Creating your database
|
Creating your database
|
||||||
|
|
Loading…
Reference in New Issue