Éric Araujo added the comment: I’m interested in an explanation of the value of doing this.
In the threading docs for example, the classes (i.e. initializers) are documented in one section, with awkward links to “Thread objects”, “Lock objects”, etc. This felt much more cumbersome to me than more modern class/attribute/method combos. Isn’t it the simplest thing to document one class, usage, constructors and all attributes, in one place? On the other hand, I don’t have the view of an outsider anymore, so I can’t say what makes sense / reads better for the doc’s audience (as opposed to doc editors). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16568> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
