Development on MySQLdb-2.0 has been progressing, and has recently moved to a Mercurial repository on SourceForge. This was imported from the SVN trunk. If you pull from the SVN trunk in the future, you may be disappointed.
2.0 is turning into a very major rewrite. I should have an alpha release soon. For now, the hg repository builds and passes all tests, but there are probably a few things that aren't thoroughly tested yet, particularly scrolling on cursors. I'll post more detail along with the alpha release.
Python3 support is not immediately in the works, and I probably won't work on it until I am close to a beta. At this point, I would target Python-3.1, maybe 3.2. 3.0 would probably work too.
4 comments:
At pycon one reoccurring theme in all the async talks (twisted, eventlib, etc) was how mysqldb was impossible to deal with in an async way due to blocking calls to mysql in the C. It always required falling back on threads.
Is there any plans in 2.0 for better async support?
Yes. I will write a separate post on this, though, because I have a long-winded explanation and history lesson.
Hi, please update site.cfg registry key to
SOFTWARE\MySQL AB\MySQL Server 5.5
Just spent 15 mins to find this :)
it seems davisphuh has already patched mysql-python-1.2.3 for python-3.2 and it works nice - I compiled&instaled it then tested it in a production environment; why not adopt these changes to the repository? https://github.com/davispuh/MySQL-for-Python-3
Post a Comment