Bug 237648 - Update MySQL-python to 1.2.1p2
Summary: Update MySQL-python to 1.2.1p2
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: MySQL-python
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tom Lane
QA Contact:
URL: http://code.djangoproject.com/wiki/Ba...
Whiteboard:
Depends On:
Blocks: 235728
TreeView+ depends on / blocked
 
Reported: 2007-04-24 14:29 UTC by Michel Alexandre Salim
Modified: 2013-07-03 03:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-01-05 03:58:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michel Alexandre Salim 2007-04-24 14:29:09 UTC
Description of problem:
The latest stable release of Django enforces a MySQL-python minimum version of
1.2.1p2 for its mysql backend, apparently due to bugs in previous versions of
MySQL-python.

They have a deprecated backend, mysql_old that currently works, but won't be
maintained (and presumably will trigger the bugs that caused them to raise the
min version in the first place).

Would it be OK to update MySQL-python? Otherwise I'll put a note in FC-5's
Django to remind users to use mysql-old.


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

How reproducible:
Always

Comment 1 Tom Lane 2008-01-05 03:58:42 UTC
Sorry this bug slipped through the cracks for awhile :-(.  But FC-5 is EOL and won't be updated any more.  
F7 and F8 have 1.2.2.


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