[Image-SIG] Re: PIL works under NT but not Win98, where to look? Doh.... Never mind found it.

John Ferguson hakuin@voicenet.com
Fri, 11 Aug 2000 23:34:06 -0400


----- Original Message -----
From: John Ferguson <hakuin@voicenet.com>
To: <image-sig@python.org>
Sent: Friday, August 11, 2000 10:40 PM
Subject: PIL works under NT but not Win98, where to look?


> I am trying to quickly get up to speed on Python for OpenGL programming.
> One of main obstacles is:
>
> >>> im = Image.open("C:\development\python\NeHe Ports\crate.bmp")
> >>> im.tostring("raw", "RGBX", 0, -1)
> Traceback (innermost last):
>   File "<stdin>", line 1, in ?
>   File "C:\Program Files\Python\PIL\Image.py", line 325, in tostring
>     self.load()
>   File "C:\Program Files\Python\PIL\ImageFile.py", line 125, in load
>     self.load_prepare()
>   File "C:\Program Files\Python\PIL\ImageFile.py", line 175, in
load_prepare
>     self.im = Image.core.new(self.mode, self.size)
>   File "C:\Program Files\Python\PIL\Image.py", line 40, in __getattr__
>     raise ImportError, "The _imaging C module is not installed"
> ImportError: The _imaging C module is not installed
>
> The exact same file pil-win32-991101.zip seems to work fine on NT, at
least
> I can get the tostring call to work.  However, my 98 box is not working.
>
> I have tested my python path:
>
> >>> print sys.path
> ['', 'C:\\Program Files\\Python', 'C:\\Program
> Files\\Python\\Lib\\plat-win', 'C:\\Program Files\\Python\\Lib',
> 'C:\\Program Files\\Python\\DLLs', 'C:\\Program
> Files\\Python\\Lib\\lib-tk', 'C:\\PROGRAM FILES\\PYTHON\\DLLs',
'C:\\PROGRAM
> FILES\\PYTHON\\lib', 'C:\\PROGRAM FILES\\PYTHON\\lib\\plat-win',
> 'C:\\PROGRAM FILES\\PYTHON\\lib\\lib-tk', 'C:\\PROGRAM FILES\\PYTHON',
> 'C:\\PROGRAM FILES\\PYTHON\\Numeric', 'C:\\PROGRAM FILES\\PYTHON\\PIL']
>
> Which includes PIL, and lib-tk which I think are the main places for the
> Image tools.
>
> I installed python using: py152.exe and the PIL library seems to be for
the
> same version.  I also installed PyOpenGL.
>
> Any ideas on how to address this?
>
> Thanks,
>
> John Ferguson
>
>
>