On 3/20/07, chasfs <[EMAIL PROTECTED]> wrote: > The problem is that the MySQLdb page says that 1.2.1p2 has no changes > that we should worry about. Why is p2 required?
Unfortunately, there is a change that we need to worry about: the thread-safety bug in MySQLdb which caused ticket #3279[1] wasn't fixed until that version, which is why we now have the version check in Django. [1] http://code.djangoproject.com/ticket/3279 -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
