Status on MySQL Connector/Python and Python v3.1

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?

Comments

Damien Lebrun

Sun Oct 18 2009, 13:43

I think you should use the same name for both branches but post one distribution for each python version you support and let easy_install (or your users) pick the right distribution. You could post a generic distribution for py 2.x and a specific one for py 3.1.

Tarek

Sun Oct 18 2009, 16:01

You could also have a single branch and let 2to3 do the work automatically by using distribute, a drop in replacement for setuptools. See http://packages.python.org/distribute and come at #distutils on freenode for help

Geert JM Vanderkelen

Mon Oct 19 2009, 05:46

Thanks for the comments!

I'm really thinking of indeed making one package, size should be OK. But I'm not sure I would like to count on '2to3' since there are features like 'abs' I would like to use eventually.

But lets first work on get it working :-)

dbr

Fri Oct 23 2009, 04:11

Can you point me to some directions on how to get and install your experimental 3.1 branch (I'm not familiar with bzr at all, and it won't emerge for me in Gentoo, but I'll get around that eventually even if I have to skip the package system)?

I don't care if it's still very rough around the edges. Thanks.

Rackeer

Fri Nov 6 2009, 17:10

Hey

have a question, I'm trying rebuilt an excel ²⁰⁰³⁄₇ app. Looking at mysql/p(j)ython solution, any advice or tutorials. Excel does alot of calculations.

Geert JM Vanderkelen

Fri Nov 6 2009, 17:40

@dbr:
Sorry, missed your question, but it's so rough it's ugly still. I hope to get a package ready before End of Year.

@Rackeer:
Excel? No.. lol?

Damien Lebrun: Sun Oct 18 2009, 13:43

I think you should use the same name for both branches but post one distribution for each python version you support and let easy_install (or your users) pick the right distribution. You could post a generic distribution for py 2.x and a specific one for py 3.1.
Tarek: Sun Oct 18 2009, 16:01

You could also have a single branch and let 2to3 do the work automatically by using distribute, a drop in replacement for setuptools. See http://packages.python.org/distribute and come at #distutils on freenode for help
Geert JM Vanderkelen: Mon Oct 19 2009, 05:46

Thanks for the comments!

I'm really thinking of indeed making one package, size should be OK. But I'm not sure I would like to count on '2to3' since there are features like 'abs' I would like to use eventually.

But lets first work on get it working :-)
dbr: Fri Oct 23 2009, 04:11

Can you point me to some directions on how to get and install your experimental 3.1 branch (I'm not familiar with bzr at all, and it won't emerge for me in Gentoo, but I'll get around that eventually even if I have to skip the package system)?

I don't care if it's still very rough around the edges. Thanks.
Rackeer: Fri Nov 6 2009, 17:10

Hey

have a question, I'm trying rebuilt an excel ²⁰⁰³⁄₇ app. Looking at mysql/p(j)ython solution, any advice or tutorials. Excel does alot of calculations.
Geert JM Vanderkelen: Fri Nov 6 2009, 17:40

@dbr:
Sorry, missed your question, but it's so rough it's ugly still. I hope to get a package ready before End of Year.

@Rackeer:
Excel? No.. lol?