bramble wrote: > On Oct 1, 10:34 pm, Benjamin <[EMAIL PROTECTED]> wrote: >> and they are still supported >> not to break compatability. > > Hm. Ok. I can see that for the 2.x releases. But Py3k is all about > breaking compatibility, so, it would seem there's more to the story.
Yes, compatibility is broken, strictly speaking; however, the goal is that the majority of changes can be handled automatically using the 2to3 tool to convert the source code. You can't really do that if you remove Tkinter entirely. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco -- http://mail.python.org/mailman/listinfo/python-list
