From: gmcm at hypernet.com (Gordon McMillan)
Date: Wed, 14 Apr 1999 01:47:48 GMT
Subject: Windows install has problems. Guido asked that I use this ne
In-Reply-To: <924040766.18823.0.nnrp-12.9e982a40@news.demon.co.uk>
References: <924040766.18823.0.nnrp-12.9e982a40@news.demon.co.uk>
Message-ID: <1288067825-21306272@hypernet.com>
X-UID: 1336                                                  

Barry Scott writes:

[troubles with tcl/tk and installer on NT]

>     As for the tcl80.dll problems. Either assume that tcl80.dll is
>     in the standard (english) installation place
>     %systemdrive%\program files\tcl\bin\tcl80.dll.
> 
>     OR release note that users must add the Tcl bin dir to there
>     PATH.

Sounds good to me.
 
>     As the python lib does not have a module to access the registry
>     it makes getting the info from the registry hard.
> 
>     Maybe 1.6 needs a windows registry module to solve this and
>     other problems.
 
Actually, the standard Python on Windows does know about the 
registry. And Mark Hammond's Win32 extension stuff has a registry 
module. 

But what if the user is (for some other purposes) relying on having a 
different version of tcl/tk around? Not all that uncommon, and very 
messy. Python is not real flexible about the version of tcl / tk it 
uses. 

- Gordon




