[PYTHON IMAGE-SIG] Re: [PYTHONWIN-SIG] New PIL experiment.
Harri Pasanen
pa@tekla.fi
Tue, 27 May 1997 09:45:44 +0300
Mark Hammond writes:
> I see a few other people got sick of the Tkinter FAQ too :-)
>
> So I took the latest PIL binaries from www.python.org, and wraped it up in
> the new installation package. The installer:
> * correctly finds Python's installation, and suggests you install under
> there.
> * Installs Tk and Tkinter correctly, and sets the environment variables.
> On 95 this is done via Autoexec.bat, on NT this is done via the registry
> (unfortunately, both require a reboot when done)
Actually, I don't think reboot is necessary on NT, not for setting the
environment variables anyway.
Instead of reboot you can lauch Control Panel/System, view the
environment page, you'll see the new environment variables from
registry there.
Just press Ok to close System, and presto, your environment
variables are in effect.
> * Allows uninstall etc.
> * Works :-)
Doesn't work for me ;-(, see below.
>
> On the down side:
> * Requires a Pythonwin 1.0 install to work.
> * Does not allow you to specify your own TK or TCL directories - always
> installed under the core install directory (default is "{Python}\Imaging"
> * No readme..
>
> You can find it at
> http://starship.skyport.net/crew/mhammond/pil.exe
>
> It would be really cool if some people on these SIGS (especially people who
> dont yet have PIL yet) could give this a try and see if it works.
>
I gave it a short run-a-round, but unfortunately no go.
PythonPath is not set up correctly, it omits the Imaging/Lib
directory.
I tweaked it from the registry to read
[HKEY_LOCAL_MACHINE\SOFTWARE\Python\PythonCore\1.4.0\PythonPath\Imaging]
@="d;\\PythonWin\\Imaging;d:\\PythonWin\\Imaging\\Lib;d:\\PythonWin\\Lib\\Tkinter"
Another option would be to replace the "d;\\PythonWin\\Imaging"
with "d;\\PythonWin\\Imaging\\Lib" and move the dll files from Imaging
to the Lib directory. This would be cleaner in my mind.
After the path modification viewer.py manages to run. It however
terminates to a weird traceback:
[d:\pythonwin\imaging]..\python Scripts\viewer.py Images\lena.gif
Traceback (innermost last):
File "Scripts\viewer.py", line 36, in ?
im = Image.open(filename)
File "d:\PythonWin\Imaging\Lib\Image.py", line 467, in open
init()
File "d:\PythonWin\Imaging\Lib\Image.py", line 84, in init
for f in os.listdir(p):
nt.error: (3, 'No such process')
This looks weird enough for me to quit at this point and let the specialists
step in ;-)
> Please remember than my intention is to split the Pythonwin installation
> into a few packages. Thus, in the future it will _not_ be necessary to
> have installed Pythonwin - only to have installed via "setup" the "core
> Python binaries". There will then be a few "Extension installers", of
> which Pythonwin (and win32com) will be just a few.
>
Looking forward to that.
Harri
_______________
IMAGE-SIG - SIG on Image Processing with Python
send messages to: image-sig@python.org
administrivia to: image-sig-request@python.org
_______________