[Image-SIG] trouble using PIL on windows

Kevin Cazabon KCAZA@cymbolic.com
Tue, 29 Feb 2000 09:41:21 -0800

I think the root of the problem is probably (as you elude to below) that Python
accepts a file named EITHER ".pyd" or ".dll" as the same, but "prefers" the "pyd"
file.  So, if you have an older version of a file as a .pyd, and you install a new
.dll, it still uses the older file.

Basically, I'd like to see Python distributions like PIL standardize on ".pyd" files
to eliminate this problem, but I do see the advantage of allowing Python itself to
access both.

Kevin Cazabon.

>>> "Jeffrey Kunce" <kuncej@mail.conservation.state.mo.us> 02/29/00 09:23AM >>>
>Hi.  Thanks for the advice.  I put the _imaging.dll in the python root
>directory (i.e. d:\python).  It still won't load.  When I type:

I had these same problems (just on Win98 - NT works fine out of the box)
I tried so many things, that I can't remember what finally fixed it :-(

Try this:

1) unzip the PIL distribution (I have pil-win32-991101.zip) into a scratch
directory. You will get a folder "py152" containing:
  PIL (folder)
  Scripts (folder)

2) move  the Scripts folder, _imaging.dll, and  _tkinter.pyd  into the PIL folder

3) move the PIL folder and PIL.pth to your python root directory
 (c:\program files\python\ or wherever).

4) search out any other files named _imaging.dll, _imaging.pyd, 
 _tkinter.dll, or  _tkinter.pyd  that might possibly be on your python path
or on your system path. Move them somewhere python can't find them.
(I got so frustrated, I moved them to a floppy).

5) see if PIL will run

Good luck!


Image-SIG maillist  -  Image-SIG@python.org