Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 235728 - Django-0.96 requires MySQLdb 1.2.1p2 or higher
Summary: Django-0.96 requires MySQLdb 1.2.1p2 or higher
Alias: None
Product: Fedora
Classification: Fedora
Component: Django
Version: 5
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Michel Alexandre Salim
QA Contact: Fedora Extras Quality Assurance
Whiteboard: bzcl34nup
Depends On: 237648
TreeView+ depends on / blocked
Reported: 2007-04-09 20:13 UTC by Chris Brand
Modified: 2008-05-06 19:29 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-05-06 19:29:27 UTC

Attachments (Terms of Use)

Description Chris Brand 2007-04-09 20:13:56 UTC
Description of problem:
Django-0.96 requires MySQLdb 1.2.1p2 or higher.
With an automatically-updated fc5 installation, you get Django 0.96 but mysqldb
1.2.0, which doesn't work.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a Django project with a MySQL backend
2. Try to use it
Actual results:
An exception because the version of MySQLdb is too old :
ImproperlyConfigured: Error importing middleware
django.contrib.sessions.middleware: "MySQLdb-1.2.1p2 or newer is required; you
have 1.2.0"

Expected results:
It should work,

Additional info:
This is documented in the release notes for 0.96 at

Comment 1 Michel Alexandre Salim 2007-04-13 23:40:49 UTC
Hmm. it looks like the easiest way is to just use the mysql_old backend; you'd
be missing out on the new features, but it will be as functional as the mysql
backend in Django 0.95.

I can change the default template's for FC5 so that it suggests
mysql_old rather than mysql, and put a notice in %doc -- that's sufficient, I hope?

Comment 2 Chris Brand 2007-04-15 01:44:07 UTC
I'm using mysql_old for now, but it took some digging to find out that it was
I'm assuming it's non-trivial to move to a newer version of mysqldb ? If so,
then your suggestion makes sense.

Comment 3 Michel Alexandre Salim 2007-04-24 13:52:23 UTC
It's technically trivial, but mysqldb comes with the main MySQL distribution,
and Fedora developers tend not to issue updates to large packages such as these
on stable releases.

Comment 4 Michel Alexandre Salim 2007-04-24 14:20:32 UTC
Uh, my mistake, it is a separate project. I'll ask the maintainer

Comment 5 Bug Zapper 2008-04-04 06:49:23 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here: to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out

Comment 6 Bug Zapper 2008-05-06 19:29:25 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.