Zachary Ware <zachary.w...@gmail.com> added the comment:
I'm closing this as a duplicate of bpo-42560 (and probably several others). Chris: in short, we know the Tkinter docs are incomplete and we welcome improvements to them, but it costs just as much to say "I don't have the time to spend on this" as it does to say "you have to make this easier for me for free" :). As far as using the official Tk docs for Tkinter: their documentation is fairly comprehensive and easily translatable, because Tkinter as a translation layer tries to be as thin as possible. You don't have to know Tcl to use their documentation beyond some very basic syntax. To add full documentation of Tkinter, we would basically have to copy all of Tk's documentation. At that point, it feels pretty pointless to do so when we can just point there in the first place (as we already do). ---------- nosy: +zach.ware resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Improve Tkinter Documentation _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue44485> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
