On Sat, Jan 13, 2001 at 04:41:09AM -0600, Gordon Sadler wrote:
> Package: python2-tk
> Version: N/A; reported 2001-01-13
> Severity: normal
>
> I haven't installed these from unstable yet. But I have had python1.52
> and python2 from p.d.o/~flight, both downloaded as source and rebuilt
> locally with tcl/tk8.3.
>
> Now that python2 is coming into unstable, is there any reason we can't
> finally update to tcl/tk8.3? It doesn't take much work, change the
> Setup file to point to correct lib dir, _tkinter.c, and tkappinit.c .
>
> Would be very appreciated, it's annoying to keep multiple versions of
> libraries around without good cause.
I'm all open for this, but I don't know what is best.
Python 1.5.2 currently is built with Tcl/Tk8.0, since back in June I was
told by both Fredrik Lundh (Tkinter) as well as our Tk maintainer David
Engel, that using 8.0 would be the safest bet.
Now I just saw that, starting with Python 1.6, Misc/NEWS says that we're now
prepared for Tcl/Tk 8.2 and 8.3; I hadn't noticed that before.
What makes me a little bit unsure is that Tcl/Tk8.3 isn't yet in testing,
but only in unstable. This means that python2 will sit in unstable until
tk8.3 moves to testing.
Also, the vast majority of packages using Tk in sid still depend on tk8.0
(60 packages), compared to tk8.2 (19 packages) and tk8.3 (18 packages).
Anyway, I guess I'll build the next package revision with Tcl/Tk8.3. I'm
also working on backporting Tkinter from Python 1.6a2 to the python-tk
package in order to make the transition complete (and in order to resolve me
from the task of installing/deinstalling the correct tk8.x-dev packages each
time I'm building python or python2 ;-).
Or does somebody think it's worthwhile to provide python2-tk8.x packages ?
Since the tk8.0-dev and tk8.3-dev still seem to conflict, the building of
the packages would be the biggest problem.
Gregor
