New submission from Steve Holden <st...@holdenweb.com>: C:\Users\sholden>\python31\python \python31\Tools\webchecker\wcgui.py Traceback (most recent call last): File "\python31\Tools\webchecker\wcgui.py", line 63, in <module> from Tkinter import * ImportError: No module named Tkinter
This makes is seem pretty clear that not even minimal effort has been expended to ensure that this Tools is functional. It's not a priority, so that's understandable. Maybe I am the only person who ever tried to use this under Python 3. Perhaps we need a test that will fail if these things don't at least run to completion (and no, I don't know how I would test wcgui, but I'd be interested in discussing test strategies)? ---------- assignee: holdenweb components: 2to3 (2.x to 3.0 conversion tool), Demos and Tools messages: 108641 nosy: holdenweb priority: high severity: normal stage: unit test needed status: open title: At least some Tools utilities are still Python 2 type: feature request versions: Python 3.1 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9083> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com