Bill> I think a PyGUI mailing list would be a good thing, Skip. And a
Bill> bug-tracker. And a CVS repository.
Bill> I disagree, though, about this discussion being too detailed for
Bill> this list. This is exactly the kind of discussion we need on this
Bill> list -- what are we going to do to fix the biggest outstanding
Bill> problem with Python 2? Discussions about what to name specific
Bill> properties might be more appropriate elsewhere -- seems like
Bill> python-dev likes those kinds of discussions :-).
On this list I think we can concluded whether or not Python 3 needs a
standard GUI toolkit. The technical discussions about what form PyGUI takes
to be that candidate (whether keyboard shortcuts should be introduced with
"&" or "_", what functionality belongs in a canvas widget, etc) belong on a
PyGUI-specific list. Someone arriving on the scene in a couple months won't
know that substantial technical discussion took place here. Once he does
realize that, he's going to have to wade through archives full of other
Python 3-related stuff to get to the PyGUI-related stuff. People discussing
other things about Python 3 aren't going to want PyGUI technical discussions
mixed in with discussions about extensions to argument passing.
Skip
_______________________________________________
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
