MySQL for Python

The mysql-python project is five years old today, and just short of a quarter of a million downloads. Somehow I've managed to move up into the top 30 project list, but I expect that's due in large part to attrition. MySQL moved their source ... [More] repository off a couple years ago and switched to BitKeeper. Guido van Rossum got tired of waiting around for Subversion support and the long delay updating the anonymous CVS servers and got a Subversion server hosted, just before SourceForge opened up Subversion for everyone. I plan to stick around and start using Subversion immediately after releasing MySQL-1.2.1. I had hoped to release MySQLdb-1.2.1 today, but some extended testing has turned up a memory leak that's been around for awhile, and I want to get that fixed first. Realistically I should have another release candidate, too. 1.3.0 will be released not too long afterwards. Plans for 1.3.x/1.4/2.0 * _mysql.c is going to be broken up into some more managable source files. * error number to exception mapping will be done with a dictionary instead of a steadily-growing case statement. It used to be reasonably small, but I'm finding a lot of new errors to map in MySQL-5.0. * prepared statement API * use_unicode=True by default (maybe mandatory) * MySQLdb.param_style will actually be a setting so you can use either the current "format" (%s) style or "qmark" (?). The latter is required for prepared statements, but I hope to be able to convert between the two. Converting a query that uses %s to ? is trivally-easy. Going the other direction requires regular expressions, but may not be too bad. * I really hate the name of the conversions module and I'm going to rename it to codecs (likely). (Why must all my sub-module names start with c?) * I might eliminate cursor classes and replace them with plug-ins. Feature requests: http://sourceforge.net/tracker/?group_id=22307&atid=374935 Bug reports: http://sourceforge.net/tracker/?group_id=22307&atid=374932 Patches: http://sourceforge.net/tracker/?group_id=22307&atid=374934 I'm seeing a fair number of downloads for 1.2.1c7 and no bugs posted, so I guess that's good. [Less]

Here's hoping the seventh time's the charm for MySQLdb-1.2.1. Consider this last call for bugs, and I hope to release 1.2.1 on March 8. Please test.

MySQL-python got second runner-up in the Database category in the 2006 Community Choice Awards, behind Firebird and phpMyAdmin. I was actually a little surprised to have made the list at all. There have been a few small bugs cropping up in ... [More] MySQLdb-1.2.1 that only affect old versions of MySQL. Some only affect 4.0 and older, and some affect 3.23 and older. If you're using 4.1 or newer, they won't affect you. None of them are security-related. I've already fixed these in Subversion and I'm going to make a patchlevel release later this week (1.2.1_p1). I also cleaned up the trove categorizations for the project because they were really screwy. A few things were on twice, and some nonsense items were on there, like Vietnamese translation (I wouldn't know where to start) and PHP support (yuck!) MS-SQL support (barf!). [Less]

MySQLdb-1.2.1 has finally been released after more than a year of on-again, off-again development. This also coincides with the migration of the source repository to Subversion. I had intended to do this after 1.2.1, but an untimely outage of the ... [More] SourceForge CVS servers accelerated the process. I intend for this to be the final release of the 1.2 series barring any serious bugs. For more details on the roadmap, see: http://sourceforge.net/forum/forum.php?thread_id=1205360&forum_id=70460 http://sourceforge.net/pm/task.php?group_project_id=46716&group_id=22307&func=browse mysql-python is now over 250,000 downloads and MySQLdb is a package in Red Hat Enterprise Linux, Fedora Core, Debian, Ubuntu, Gentoo, Blastwave.org (Solaris packages), a couple BSDs, and probably a few more I don't know about. It's also used by projects like Django, Turbogears, Dabo, Zenoss, ViewCVS, Zope, and others. While it's been five years at SourceForge, the original project is now seven years old; I realized this when migrating the CVS repository. I feel like I need a cake or something. [Less]

1.2.2b3 will probably be the final release before 1.2.2, though there may be a release candidate. I expect to release 1.2.2 during PyCon 2007. Good news for Windows users: The Windows build should now work out of the box without any patching or ... [More] hacking, so long as you are building against MySQL-5.0; if you are building against another version, minor hacking is required for now. As usual, I do not (and can not) make Windows binaries. If you have one to contribute, let me know. Most likely users will want MySQL-5.0 and Python-2.4 or 2.5, which means two different builds. Please build against stock packages (i.e. the python.org and mysql.com ones). If it makes you feel any better, I don't build packages for Linux anymore either. But then, the Linux vendors seem to have that covered, so I don't have to. 1.2.2 will almost certainly be the final release of the 1.2 series. I have some fixes that need to be merged back into the trunk before I can start working on 1.3/1.4/2.0 again. If you have any interest in working on new features for the trunk, let me know. One of the big features that will need a lot of work is the prepared statements API. You will definitely need to be a good C coder to work on that. A couple people have previously offered to work on it in the last year; yes, I am talking to you. [Less]

I'll be attending the MySQL Conference this year. For more (but not much more) details, see the new developer blog: http://mysql-python.blogspot.com/

Here's hoping the seventh time's the charm for MySQLdb-1.2.1. Consider this last call for bugs, and I hope to release 1.2.1 on March 8. Please test.

MySQL-python got second runner-up in the Database category in the 2006 Community Choice Awards, behind Firebird and phpMyAdmin. I was actually a little surprised to have made the list at all. There have been a few small bugs cropping up in ... [More] MySQLdb-1.2.1 that only affect old versions of MySQL. Some only affect 4.0 and older, and some affect 3.23 and older. If you're using 4.1 or newer, they won't affect you. None of them are security-related. I've already fixed these in Subversion and I'm going to make a patchlevel release later this week (1.2.1_p1). I also cleaned up the trove categorizations for the project because they were really screwy. A few things were on twice, and some nonsense items were on there, like Vietnamese translation (I wouldn't know where to start) and PHP support (yuck!) MS-SQL support (barf!). [Less]

I'll be attending the MySQL Conference this year. For more (but not much more) details, see the new developer blog: http://mysql-python.blogspot.com/

The mysql-python project is five years old today, and just short of a quarter of a million downloads. Somehow I've managed to move up into the top 30 project list, but I expect that's due in large part to attrition. MySQL moved their source ... [More] repository off a couple years ago and switched to BitKeeper. Guido van Rossum got tired of waiting around for Subversion support and the long delay updating the anonymous CVS servers and got a Subversion server hosted, just before SourceForge opened up Subversion for everyone. I plan to stick around and start using Subversion immediately after releasing MySQL-1.2.1. I had hoped to release MySQLdb-1.2.1 today, but some extended testing has turned up a memory leak that's been around for awhile, and I want to get that fixed first. Realistically I should have another release candidate, too. 1.3.0 will be released not too long afterwards. Plans for 1.3.x/1.4/2.0 * _mysql.c is going to be broken up into some more managable source files. * error number to exception mapping will be done with a dictionary instead of a steadily-growing case statement. It used to be reasonably small, but I'm finding a lot of new errors to map in MySQL-5.0. * prepared statement API * use_unicode=True by default (maybe mandatory) * MySQLdb.param_style will actually be a setting so you can use either the current "format" (%s) style or "qmark" (?). The latter is required for prepared statements, but I hope to be able to convert between the two. Converting a query that uses %s to ? is trivally-easy. Going the other direction requires regular expressions, but may not be too bad. * I really hate the name of the conversions module and I'm going to rename it to codecs (likely). (Why must all my sub-module names start with c?) * I might eliminate cursor classes and replace them with plug-ins. Feature requests: http://sourceforge.net/tracker/?group_id=22307&atid=374935 Bug reports: http://sourceforge.net/tracker/?group_id=22307&atid=374932 Patches: http://sourceforge.net/tracker/?group_id=22307&atid=374934 I'm seeing a fair number of downloads for 1.2.1c7 and no bugs posted, so I guess that's good. [Less]