-
-
Notifications
You must be signed in to change notification settings - Fork 343
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
How-to guides #1291
Comments
I think this is a duplicate of #472? |
Yep. |
BTW, that was also inspired by that post – it's a pretty good post, isn't it? :-) If you have a minute, it'd be great if you could check #472 and make sure all your ideas for howto topics are captured there – we don't want to lose those! |
I'd be interested in seeing the example for "interact with a repl, pexpect-style", but couldn't find anything in the other issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
"What nobody tells you about documentation" distinguishes four types of documentation:
Of these, Trio docs are weakest on the "how-to guides" section. Currently there are a lot of hidden gems in chat, gists, and issues. That may be because Trio's evolving too quickly to have a stable set of how-tos. But as the API settles it would be nice to have vetted answers to common "how do I ___?" situations.
Even before 1.0 it would be nice to display the current status of each how-to so I don't have to keep track of the mental bookmarks I've saved for each task, and ask on chat to makes sure the 2-year-old gist is still the preferred way.
Also nice: having recommendations tested in CI so they don't fall out of date.
That includes how-tos which may involve third-party libraries, like triopg or asyncssh.
Some examples include: "How do I"...
The text was updated successfully, but these errors were encountered: