On Tue, 2007-10-02 at 03:04 +0000, bramble wrote: > But Py3k is all about breaking compatibility
That's a complete distortion of Python 3.0's mission. Python 3.0 breaks backwards compatibility only where there exist good reasons to do so. As Guido put it in a recent Python-3000 post, "Python 3000 is boldly choosing to be backwards compatible, except in cases where a real benefit can be obtained by being incompatible." So, unless you can make a case that a real benefit can be obtained by removing Tkinter, it'll stay. -- Carsten Haese http://informixdb.sourceforge.net -- http://mail.python.org/mailman/listinfo/python-list
