Home |  MySQL Buzz |  FAQ |  Feeds |  Submit your blog feed |  Feedback |  Archive |  Aggregate feed RSS 2.0 English Deutsch Español Français Italiano 日本語 Русский
Status on MySQL Connector/Python and Python v3.1
+3 Vote Up -0 Vote Down

This weekend I've been busy porting MySQL Connector/Python to Python 3.1 in a new experimental branch. It is quite a challenge and I was advised to actually rewrite the whole thing for Py3K. However, after crawling through the TypeErrors and other exceptions I figured I did good with porting the code. It helps to re-factor some ancient, weird lines of code and learns me the new goodies coming with Python v3.1.

Status: examples are somehow working, but not all unittests. So we are like 60% away from having MySQL under Python 3.1.

I must say that I love Python 3.1! Especially the Text and Data concept! The major caveat is that we'll have to maintain 2 branches since it's totally incompatible with previous Python versions.

So how we are going to name Python 2K and 3K branches? Shall we pack both Python v2.x and v3.x in the same package and let the setup tools decide what to install? I'm favoring this, so there is no "What shall I download?" confusion.

Universal Python Eggs anyone?

Votes:

You must be logged in with a MySQL.com account to vote on Planet MySQL entries. More information on PlanetMySQL voting.

Planet MySQL © 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Sun Microsystems, Inc. and does not
necessarily represent the opinion of Sun Microsystem, Inc. or any other party.