New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A Better Help File #66881
Comments
Just the General Help that is in Python, doesn't really help. Here's what would help, if every Module, had an example in code of how it was used instead of the Trees. I mean, word trees, well that's what the writing reminds me of, is word trees like you'd produce in an English class. But, a short working piece of code, does allot more for me, than a lecture, you'd have to take a course to understand because of it's use of it's own writing style. It doesn't help to type help() and hit enter. |
Just the General Help that is in Python, doesn't really help. Here's what would help, if every Module, had an example in code of how it was used instead of the Trees. I mean, word trees, well that's what the writing reminds me of, is word trees like you'd produce in an English class. But, a short working piece of code, does allot more for me, than a lecture, you'd have to take a course to understand because of it's use of it's own writing style. It doesn't help to type help() and hit enter. Honestly, the old old version of Quick Basic, that once came with every version of windows back in the 90s. It's help, is a template that I think Python, should follow. |
The help isn't targeted at teaching you to use the module. The help is targeted at *reminding* you how to use the module after you've read the full documentation, which usually does contain examples (though generally not at the top of the page...they are usually at the bottom or interspersed...it is a *reference* guide after all, the tutorial is a separate thing with yet a different target). I'm afraid, though, that if you find the help to be a wall of words, you'll find the library reference worse. You might be best serve by checking out the book/website "Python Module of the Week" (pymotw.com), which has a more tutorial style and more examples. I've never see the Quick Basic style docs. I don't know if that style would be applicable to Python modules. Bottom line right now, though, is that this isn't really a useful issue for the bug tracker. If you want to discuss strategies for making overall improvements in the documentation, that's something that should be done with the group of people who focus on documentation. Their mailing list is docs@python.org if you want to join the team and advocate for a change (your suggestion has already been posted to that mailing list by the bug tracker, FYI). |
I've written several languages, I'm no novice but, I also know when to brush -----Original Message----- R. David Murray added the comment: The help isn't targeted at teaching you to use the module. The help is I've never see the Quick Basic style docs. I don't know if that style would Bottom line right now, though, is that this isn't really a useful issue for ---------- Python tracker <report@bugs.python.org> |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: