Tcl/Tk Path problems in Python 1.5.2 installation

[wes weston]

David,
	I just had a heck of a time doing something similar. On NT, I had an
old version of tcl - which I removed. After that, Tk quit working. I
found the problem by doing a find *.dll in my tcl tree. That yielded
about six dll's. About four of these were also in winnt/system32. The
one causing the problem was tk80.dll.
		wes

David Nichols wrote:
> 
> I just installed python 1.5.2 (running py152.exe and answering 'yes - I
> want to install Tcl/Tk') and have been unable to get the path set
> up correctly for graphical applications.  For instance, if I go to the
> idle directory (//E/Programs/Py152/Tools/idle) and try to launch it I
> get the following result.
> 
> ============================================================
> BASH.EXE-2.02$ python idle.py
> Traceback (innermost last):
>   File "idle.py", line 3, in ?
>     PyShell.main()
>   File "E:\Programs\Py152\Tools\idle\PyShell.py", line 611, in main
>     root = Tk()
>   File "E:\Programs\Py152\Lib\lib-tk\Tkinter.py", line 886, in __init__
>     self.tk = _tkinter.create(screenName, baseName, className)
> TclError: Can't find a usable init.tcl in the following directories:
>     {} ./lib/tcl8.0 . E:/Programs/Py152/tcl8.0/library
> E:/Programs/Py152/Tools/library
> 
> This probably means that Tcl wasn't installed properly.
> ============================================================
> 
> The directories in sys.path are as follows ...
> E:\PROGRAMS\PY152
> E:\PROGRAMS\PY152\DLLs
> E:\PROGRAMS\PY152\PIL
> E:\PROGRAMS\PY152\lib
> E:\PROGRAMS\PY152\lib\lib-tk
> E:\PROGRAMS\PY152\lib\plat-win
> E:\Programs\Py152\DLLs
> E:\Programs\Py152\Lib
> E:\Programs\Py152\Lib\lib-tk
> E:\Programs\Py152\Lib\plat-win
> 
> Tcl in installed in E:\PROGRAMS\Py152\\Tcl, and init.tcl exists in
> E:\PROGRAMS\Py152\Tcl\lib\tcl8.0 ... but this directory does not
> seem to be searched.
> 
> Do I need to set additional environmental variables or make changes
> to the registry beyond those made by the installer?
> 
> Thanks in advance for any help
> 
> David Nichols
> Source Signal Imaging
> dnichols at sourcesignal.com