Mailing List Archive

Richard GRUET <rgruet@ina.fr> wrote in <3714D8FF.634655C5@ina.fr>:

>cl problems:
>---------------
>shared by many ! see Hoon Yoon for instance... wish80;exe works (hence I
>conclude that tcl is installed properly) but IDLE or Tkdb don't, with
>insults like:
>C:/PROGRA~1/PYTHON/TCL/lib/tk8.0/tk.tcl: bad event type
>bad event type or keysym "MouseWheel"
> while executing
>"bind Listbox <MouseWheel> {
> %W yview scroll [expr - (%D / 120) * 4] units
>}"
> (file "C:/PROGRA~1/PYTHON/TCL/lib/tk8.0/listbox.tcl
> invoked from within
>"source [file join $tk_library listbox.tcl]"
> (file "C:/PROGRA~1/PYTHON/TCL/lib/tk8.0/tk.tcl" lin
> invoked from within
>"source C:/PROGRA~1/PYTHON/TCL/lib/tk8.0/tk.tcl"
> ("uplevel" body line 1)
> invoked from within
>"uplevel #0 [list source $tkfile]"
>
>This probably means that Tk wasn't installed properly.
>

I had exactly that problem. I think it means that you upgraded an old Tcl
system but there are still copies of the old Tcl80.dll files lying around
somewhere and python is finding those in preference to the new ones.
Delete tcl80.dll from the \winnt\system32 directory or wherever they
are, and add the tcl bin directory (e.g. D:\Progra~1\Tcl\Bin) to the end of
your path in the control manager/system/environment settings.

--
Duncan Booth duncan@dales.rmplc.co.uk
int month(char *p){return(124864/((p[0]+p[1]-p[2]&0x1f)+1)%12)["\5\x8\3"
"\6\7\xb\1\x9\xa\2\0\4"];} // Who said my code was obscure?
http://dales.rmplc.co.uk/Duncan

> Registry problems:
I have the exact same problems, I removed the previous version (1.5.1) of
Python before I installed 1.5.2.


/FN

Richard GRUET wrote:
> Tcl problems:
> ---------------
> shared by many ! see Hoon Yoon for instance... wish80;exe works (hence I
> conclude that tcl is installed properly) but IDLE or Tkdb don't, with
> insults like:
> C:/PROGRA~1/PYTHON/TCL/lib/tk8.0/tk.tcl: bad event type
> bad event type or keysym "MouseWheel"
> while executing
> "bind Listbox <MouseWheel> {
> %W yview scroll [expr - (%D / 120) * 4] units
> }"
> (file "C:/PROGRA~1/PYTHON/TCL/lib/tk8.0/listbox.tcl
> invoked from within
> "source [file join $tk_library listbox.tcl]"
> (file "C:/PROGRA~1/PYTHON/TCL/lib/tk8.0/tk.tcl" lin
> invoked from within
> "source C:/PROGRA~1/PYTHON/TCL/lib/tk8.0/tk.tcl"
> ("uplevel" body line 1)
> invoked from within
> "uplevel #0 [list source $tkfile]"
>
> This probably means that Tk wasn't installed properly.

It means that you have several conflicting versions of Tk
installed on your machine (or rather, that Python is picking
up a version of tk80.dll that is older than the library files).

Most likely, you'll find the offender in the system directory.

See the thread "Tkinter, bad event type" for more info.

</F>

--------------153EC408423E7B5E059BA478
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Duncan Booth a =E9crit :

> Richard GRUET <rgruet@ina.fr> wrote in <3714D8FF.634655C5@ina.fr>:
>
> >Tcl problems:
> >---------------
> >......
> >
> >This probably means that Tk wasn't installed properly.
> >
>
> I had exactly that problem. I think it means that you upgraded an old T=
cl
> system but there are still copies of the old Tcl80.dll files lying arou=
nd
> somewhere and python is finding those in preference to the new ones.
> Delete tcl80.dll from the \winnt\system32 directory or wherever they
> are, and add the tcl bin directory (e.g. D:\Progra~1\Tcl\Bin) to the en=
d of
> your path in the control manager/system/environment settings.

You're right, I have an old Tcl80.dll in my windows\system32 directory. I=
've
removed it and added the Tcl\bin path to my Path variable.
The old problem disappeared, but now when I launch for instance idle.pyw,=
I get
an error:
"The procedure entry point _Tcl_Gets could not be located in the dynamic =
linl
library tcl80.dll".

There is no other copy of Tcl80.dll anywhere on my computer. My Tcl80.dll=
is
362 Kb and dated 99/03/08; and it actually doesn't export any _Tcl_Gets
procedure !! I precise that during install of the Python upgrade to 1.5.2=
, I've
selected the Tcl upgrade.

Do you know the reason for that problem ?

Thanks

Richard

--------------153EC408423E7B5E059BA478
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<i>Duncan Booth a &eacute;crit :</i>
<blockquote TYPE=CITE><i>Richard GRUET &lt;rgruet@ina.fr> wrote in &lt;3714D8FF.634655C5@ina.fr>:</i><i></i>
<p><i>>Tcl problems:</i>
<br><i>>---------------</i>
<br><i>>......</i>
<br><i>></i>
<br><i>>This probably means that Tk wasn't installed properly.</i>
<br><i>></i><i></i>
<p><i>I had exactly that problem. I think it means that you upgraded an
old Tcl</i>
<br><i>system but there are still copies of the old Tcl80.dll files lying
around</i>
<br><i>somewhere and python is finding those in preference to the new ones.</i>
<br><i>Delete tcl80.dll from the \winnt\system32 directory or wherever
they</i>
<br><i>are, and add the tcl bin directory (e.g. D:\Progra~1\Tcl\Bin) to
the end of</i>
<br><i>your path in the control manager/system/environment settings.</i></blockquote>
You're right, I have an old Tcl80.dll in my windows\system32 directory.
I've removed it and added the Tcl\bin path to my Path variable.
<br>The old problem disappeared, but now when I launch for instance idle.pyw,
I get an error:
<br>"The procedure entry point _Tcl_Gets could not be located in the dynamic
linl library tcl80.dll".
<p>There is no other copy of Tcl80.dll anywhere on my computer. My Tcl80.dll
is 362 Kb and dated 99/03/08; and it actually doesn't export any _Tcl_Gets
procedure !! I precise that during install of the Python upgrade to 1.5.2,
I've selected the Tcl upgrade.
<p>Do you know the reason for that problem ?
<p>Thanks
<p>Richard</html>

--------------153EC408423E7B5E059BA478--

Forget what I've just written: I've just removed tk80.dll (in addition to=

tcl80;dll) from the system32 directory, and this time all worked fine.

So the final solution is :
- remove any extra copy of tcl80.dll and tk80.dll except the ones in tcl\=
bin
directory
- add tcl\bin directory to the Path environment variable.

Thanks for your help

Richard


Duncan Booth a =E9crit :

> Richard GRUET <rgruet@ina.fr> wrote in <3714D8FF.634655C5@ina.fr>:
>
> >cl problems:
> >---------------
> >shared by many ! see Hoon Yoon for instance... wish80;exe works (hence=
I
> >conclude that tcl is installed properly) but IDLE or Tkdb don't, with
> >insults like:
> >C:/PROGRA~1/PYTHON/TCL/lib/tk8.0/tk.tcl: bad event type
> >bad event type or keysym "MouseWheel"
> > while executing
> >"bind Listbox <MouseWheel> {
> > %W yview scroll [expr - (%D / 120) * 4] units
> >}"
> > (file "C:/PROGRA~1/PYTHON/TCL/lib/tk8.0/listbox.tcl
> > invoked from within
> >"source [file join $tk_library listbox.tcl]"
> > (file "C:/PROGRA~1/PYTHON/TCL/lib/tk8.0/tk.tcl" lin
> > invoked from within
> >"source C:/PROGRA~1/PYTHON/TCL/lib/tk8.0/tk.tcl"
> > ("uplevel" body line 1)
> > invoked from within
> >"uplevel #0 [list source $tkfile]"
> >
> >This probably means that Tk wasn't installed properly.
> >
>
> I had exactly that problem. I think it means that you upgraded an old T=
cl
> system but there are still copies of the old Tcl80.dll files lying arou=
nd
> somewhere and python is finding those in preference to the new ones.
> Delete tcl80.dll from the \winnt\system32 directory or wherever they
> are, and add the tcl bin directory (e.g. D:\Progra~1\Tcl\Bin) to the en=
d of
> your path in the control manager/system/environment settings.
>
> --
> Duncan Booth duncan@dales.rmplc.co.u=
k
> int month(char *p){return(124864/((p[0]+p[1]-p[2]&0x1f)+1)%12)["\5\x8\3=
"
> "\6\7\xb\1\x9\xa\2\0\4"];} // Who said my code was obscure?
> http://dales.rmplc.co.uk/Duncan