On May 16, 5:56 am, mw <[EMAIL PROTECTED]> wrote: > Yeah I'm still at a loss on this bug. > > I ran the code provided in the thread. > Django's > django > /Library/Python/2.5/site-packages/django/__init__.pyc > pil > /Library/Python/2.5/site-packages/PIL/__init__.pyc > > And then Apache's is > django > /Library/Python/2.5/site-packages/django/__init__.pyc > pil > /Library/Python/2.5/site-packages/PIL/__init__.pyc > > As far as I can tell there is no difference! Apache still seems to be > rejecting the image as an invalid image while the Django test server > doesn't. What could the problem possibly be between the two > servers? :-(
Sounds like you are having 32/64 bit issues. You need to take extra steps to ensure on MacOSX Leopard that Python modules are compiled with 64 bit support as well as 32 bit support. For further information see: http://code.google.com/p/modwsgi/wiki/InstallationOnMacOSX This is from mod_wsgi documentation but has same issues as mod_python. Read section 'Missing Code For Architecture'. Mentions PIL as an example. Graham > On May 6, 12:38 pm, mw <[EMAIL PROTECTED]> wrote: > > > Ahh, after running the code with both the django server and apache and > > mod_python there are different paths listed. > > > I shall investigate on my own and come back if I need more help! > > > Thank you both very much! > > mw > > > On May 5, 7:13 pm, "Chatchai Neanudorn" <[EMAIL PROTECTED]> wrote: > > > > When I installed my web at webfaction I did this to see which module > > > python > > > use, > > > > at settings.py > > > > import os > > > import django, PIL > > > logfile = open('path.log', 'w') > > > > django_path = django.__file__ > > > pil_path = PIL.__file__ > > > > logfile.write('django - %\n pil - %s\n' % (django_path, pil_path)) > > > > logfile.close() > > > > ... > > > > With this code, you can see which module you are using. > > > > I can successfully install my web with this trip. > > > > Regards > > > > 2008/5/5 TP <[EMAIL PROTECTED]>: > > > > > Could you have different PYTHONPATH settings for mod_python vs command > > > > line where you're running the admin server? Different versions of PIL > > > > or something between those two versions? libjpeg and friends installed > > > > in non-standard locations where they're found by the command line > > > > python but not the python being loaded by mod_python? > > > > > On May 2, 5:02 pm, mw <[EMAIL PROTECTED]> wrote: > > > > > Hello, > > > > > > I've emailed the mailing list in the past because of problems with PIL > > > > > and and image field upload in the admin interface. The problem, just > > > > > got weirder. > > > > > > I noticed that images were never validating as actual images and were > > > > > constantly being rejected. Out of a hunch, I fired up the django > > > > > built-in server and tried the same page with the same image. This > > > > > time, the image validated and it was correctly uploaded. > > > > > > Does anyone happen to know what would then be stopping the code from > > > > > validating the image upload when run through apache instead of the > > > > > django development server? > > > > > > I'm using the SVN of django on OS X. > > > > > > Thanks in advance, > > > > > mw --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
