>The IDLE-dev mailing list is one of many hosted by python.org. See >http://www.python.org/community/lists/ for the link to the complete list >here: http://mail.python.org/mailman/listinfo I saw that. Only the main python discussion list is a newsgroup?
>If you would prefer other formats, the mailing list is mirrored >elsewhere. In particular, gmane.org offers a bi-directional mirror of >the list is several formats, including web-based blog and NNTP newsfeeds: I am using old.nabble.com. But for someone not used to this stuff it is quite hard to get in compared to a forum. Maybe these alternative ways should be mentioned on the idle-dev list site http://mail.python.org/mailman/listinfo/idle-dev http://mail.python.org/mailman/listinfo/idle-dev or on the IDLE homepage. >There is a newly written Python Developer's Guide which describes the >whole process of how to develop and contribute fixes and features for >Python in general. It applies to IDLE as well: > > http://docs.python.org/devguide/ this sounds good, I will take a look at that >... >term, a replacement for IDLE using a more modern GUI interface would be >an interesting project. That really means finding a replacement for >Tkinter in the standard library. One of the most promising efforts for >that is Greg Ewing's PyGUI project: > > http://www.cosc.canterbury.ac.nz/greg.ewing/python_gui/ I'd love to see that project florish, too. But Tkinter does look native with ttk. And it is very easy to use. >In the mean time, both IDLE and Tkinter are underrepresented in the >Python development community. They both could use more help. Your I could not agree more, IDLE simply gets lost. >And yet another big area is documentation for IDLE. Currently, it is >very sparse, between IDLE's build-in help file and the standard docs. >The source for both are included in the source tree so doc patches for >them would also be very welcome. Doc patches seem really complicated to me. What about a wiki? I would like to make my suggestions more concrete: * easy access to idle-dev and/or description on the IDLE homepage * a wiki for IDLE development * a wiki for using IDLE * a bug-tracker aside from Python bug-tracker * a feature-tracker * all this accessible from the homepage * an invitation to contribute on the IDLE startup console or at least the about window and installer =Phelix= -- View this message in context: http://old.nabble.com/Suggestions-idle-dev-tp31383544p31385979.html Sent from the Python - idle-dev mailing list archive at Nabble.com. _______________________________________________ IDLE-dev mailing list IDLE-dev@python.org http://mail.python.org/mailman/listinfo/idle-dev
