On Dec 7, 8:38 pm, Ian Clelland <clell...@gmail.com> wrote: > > 3. Code speaks, I know -- what's the best way to share this? I've sent > Vinay a patch, but that's for his Py3k branch, and might not get the > audience that something like this needs. I'm doing it for Py3k support, but > ideally it would work just as well under Python 2.x. Should I set up a > public repository somewhere, or just open a ticket and attach patches? > > Thoughts? Flames?
Ian, I have a clone of Dāvis' repo which supports MySQLdb on Python 3: https://github.com/vsajip/MySQL-for-Python-3 (forked from https://github.com/davispuh/MySQL-for-Python-3) I mentioned in a message to you that I couldn't use it because it used str.format rather than % formatting, but actually that was easy enough to patch. I didn't have to make the Django changes called for in your patch, and the test suite is running now with the MySQLdb backend. I got some warnings for utf-8 bytestrings as fixtures were loaded, but it's run the first 275 or so tests without errors or failures so I'm going to let it run to see how far it gets. I will push my changes to the above repo soon. Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
