[1.7.x] Removed a note about old versions of MySQLdb.

Django requires MySQLdb version 1.2.1p2 or later.

.. 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.

At the time of writing, the latest release of MySQLdb (1.2.5) doesn't support

Python 3. In order to use MySQLdb under Python 3, you'll have to install

``mysqlclient`` instead.

.. note::

    There are known issues with the way MySQLdb converts date strings into

    datetime objects. Specifically, date strings with value 0000-00-00 are

    valid for MySQL but will be converted into None by MySQLdb.

    This means you should be careful while using loaddata/dumpdata with rows

    that may have 0000-00-00 values, as they will be converted to None.

    datetime objects. Specifically, date strings with value ``0000-00-00`` are

    valid for MySQL but will be converted into ``None`` by MySQLdb.

.. note::

    At the time of writing, the latest release of MySQLdb (1.2.4) doesn't

    support Python 3. In order to use MySQLdb under Python 3, you'll have to

    install ``mysqlclient``.

    This means you should be careful while using :djadmin:`loaddata` and

    :djadmin:`dumpdata` with rows that may have ``0000-00-00`` values, as they

    will be converted to ``None``.

mysqlclient

~~~~~~~~~~~