On Thu, 2008-07-17 at 16:43 -0400, Ned Batchelder wrote: > Here's what I got, I have no idea if I need to do anything unusual to > change the python path or anything: > > nedbat.coke ~> python > Python 2.3.5 (#2, Oct 16 2006, 19:19:48) > [GCC 3.3.5 (Debian 1:3.3.5-13)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>> import MySQLdb > >>> MySQLdb.version_info > (1, 2, 1, 'gamma', 3) > >>> > nedbat.coke ~> python2.4 > Python 2.4.4 (#2, Apr 29 2008, 08:45:14) > [GCC 3.3.5 (Debian 1:3.3.5-13)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>> import MySQLdb > >>> MySQLdb.version_info > (1, 2, 1, 'gamma', 3) > >>>
Thanks for the rapid feedback, Ned. That's a little problematic, since it's the old release they've been using forever and was a release prior to 1.2.1-final and has known showstopper-style bugs. That version of MySQLdb doesn't work with Django's mysql backend and the mysql_old backend is going to be removed in 1.0. However, Jake Elliot (elsewhere in this thread) indicates that they're using a more recent version somewhere else on Dreamhost. So now I'm just confused, but maybe it's not all doom and gloom for the Dreamhost people. In any case, if Dreamhost aren't using 1.2.1-final2 or later -- such as 1.2.2 -- then they won't be able to say that they're supporting anything later than tomorrow's subversion checkout of Django, I suspect. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
