Do we prefer Tk8.0 or 8.2 ? (for python-tk, that is)

I have a quite urgent problem while polishing the new Python packages: Do we prefer our packages to use tk8.2 or on tk8.0 ? Python's Tkinter extension module (package python-tk) needs to be linked to libtk. I wonder if I should stay with libtk8.0 or switch to libtk8.2 for the final potato package

RFC: New package "python"

I'd like to hear your comments about a change which may or may not make it into potato: Currently "python" is an virtual package only, provided by python-base. I'd like to turn "python" into a real package with the upcoming new revision of the Python packages: Package: python Source: python Depe

Re: RFC: New package "python"

On Tue, Jan 11, 2000 at 04:48:53PM +0100, Gregor Hoffleit wrote: > I'd like to hear your comments about a change which may or may not make it > into potato: > > Currently "python" is an virtual package only, provided by python-base. I'd > like to turn "python" into a real package with the upcoming

Re: Do we prefer Tk8.0 or 8.2 ? (for python-tk, that is)

On Tue, 11 Jan 2000, Gregor Hoffleit wrote: > I have a quite urgent problem while polishing the new Python packages: > > Do we prefer our packages to use tk8.2 or on tk8.0 ? <...> > Any opinions ? A quick peek at www.python.org reveals references to nothing later than tk8.0.5, so tk8.0 would b