Skip to content
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

Fix variable names in docstring example for serve_tcp #597

Merged
merged 1 commit into from
Aug 13, 2018
Merged

Fix variable names in docstring example for serve_tcp #597

merged 1 commit into from
Aug 13, 2018

Conversation

shuckc
Copy link
Contributor

@shuckc shuckc commented Aug 13, 2018

As discussed https://gitter.im/python-trio/general?at=5b702354a6af14730b25304e this is a small patch to example code in a doc string.

@codecov
Copy link

codecov bot commented Aug 13, 2018

Codecov Report

Merging #597 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #597   +/-   ##
=======================================
  Coverage   99.31%   99.31%           
=======================================
  Files          91       91           
  Lines       10823    10823           
  Branches      753      753           
=======================================
  Hits        10749    10749           
  Misses         56       56           
  Partials       18       18
Impacted Files Coverage Δ
trio/_highlevel_open_tcp_listeners.py 100% <ø> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cdf114f...d44daca. Read the comment docs.

@pquentin pquentin merged commit cf6616c into python-trio:master Aug 13, 2018
@pquentin
Copy link
Member

Thank you @shuckc! Merged in master.

@njsmith
Copy link
Member

njsmith commented Aug 13, 2018

Thanks, and welcome! 🎉 🎂 And, no pressure, but if you'd like to keep contributing then we'd love to have you, so I'm sending you a github invite now. You can read more about this in our contributing documentation.

@njsmith
Copy link
Member

njsmith commented Aug 13, 2018

Whoops, you're already a member, nevermind :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants