MySQL Connector/Python v1.0.5 beta is now available for download from the MySQL website. This version is feature complete and we welcome and appreciate feedback and bug reports. We’re also interested in hearing your feedback for future enhancements. Let us know how you’re using the connector too, especially if you are using it with Django, SQLAlchemy and similar Python technologies. A few things have changed since the last development releases and we hope the manual shipping with the Connector/Python distribution (and also available online soon) will help you get up to speed.

I’m currently figuring out how to name the MySQL Connector/Python distributions so it works well with PyPi. Source archives would be named like mysql-connector-python-X. Y.Z.tar.gz. The name metadata would be ‘MySQL Connector Python’, thus without any underscores or dashes. This works OK, but if people have objections, please leave a comment.

This post explains how to compile Python v3.2 including support for the GNU Readline Library on MacOS X 10.7 (Lion), not using tools like MacPorts. One of the problems we try to solve is making history work in the interactive Python interpreter. Pre-requirement is to have Apple’s XCode installed (check the Appstore). First, you need a fresh copy of the GNU Readline Library and compile it. At the time of writing, readline v6.

Two extra tips when you try to (manually) bootstrap MySQL on Windows from the command line: When bootstrapping, use --no-defaults or --defaults-file. Use --standalone when starting the MySQL server. The first point really bugged me yesterday. I’m used to installing MySQL manually and having no option files available where MySQL would read them by default. On Windows, however, I used the MySQL installer. So, when I launch unit testing for Connector/Python it bugged me saying log files of InnoDB didn’t match the configuration.

I was asked whether it was possible to use more descriptive URLs for my blog posts instead of using the post ID only. Wordpress permalinks only allow to have one structure active, but that doesn’t mean you can’t change the webserver (lighttpd in my case) to do some redirections. Until an hour ago, my blog accepted only the following kind of url: http://example.com/post/871 This was, in my opinion, easier to use since shorter.