#8585: InterfaceError with MySQLdb set_character_set
--------------------------------------+-------------------------------------
          Reporter:  khsing           |         Owner:  nobody    
            Status:  new              |     Milestone:  1.0       
         Component:  Admin interface  |       Version:  1.0-beta-1
        Resolution:                   |      Keywords:            
             Stage:  Unreviewed       |     Has_patch:  0         
        Needs_docs:  0                |   Needs_tests:  0         
Needs_better_patch:  0                |  
--------------------------------------+-------------------------------------
Comment (by kmtracey):

 I doubt this is a bug in Django.  Given the error and the fact that it
 works from the development server console I'd guess for some reason when
 running under Apache the wrong shared library is being loaded or
 something.  From a console you could try:

 {{{
 python -v
 import MySQLdb
 }}}

 That will print out where MySQLdb is being loaded from in the case where
 it works.  If that looks different than the
 build/bdist.linux-x86_64/egg/MySQLdb location being used by Apache that
 would be a clue.

 (Actually from your previous note -- though the formatting didn't work --
 the MySQLdb you built should be under /usr/lib64/python2.4/site-
 packages/MySQLdb?  That doesn't look to be where it is getting pulled from
 when Apache/mod_ptyhon runs, which could be the problem.)

-- 
Ticket URL: <http://code.djangoproject.com/ticket/8585#comment:2>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to