On Dec 8, 6:46 am, Ian Clelland <clell...@gmail.com> wrote: > There also seem to be a number of unicode-related errors there (mixed > collations; unrecognized characters) -- Could that be related to the lines > in your patched mysql/base.py: > > if not PY3: > kwargs['use_unicode'] = True > > use_unicode used to be unconditional on the database connection; now you've > removed it, but just for Python 3.
I removed it because the Python 3 adapter doesn't recognise the kwarg; I thought it might be that under Python 3 it would be implicitly true. Possibly I need to check the detail of where that value is used in the 2.x adapter and see what the 3.x adapter does in that area. 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.
