Bug 237648

Summary: Update MySQL-python to 1.2.1p2
Product: [Fedora] Fedora Reporter: Michel Alexandre Salim <michel.salim>
Component: MySQL-pythonAssignee: Tom Lane <tgl>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5CC: hhorak
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#EnforcingMySQLdbversion
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-01-05 03:58:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 235728    

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.