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 bad variable used #2034

Merged
merged 1 commit into from
Jun 28, 2017
Merged

Fix bad variable used #2034

merged 1 commit into from
Jun 28, 2017

Conversation

cecton
Copy link
Contributor

@cecton cecton commented Jun 28, 2017

What do these changes do?

It fixes a wrong variable being used. This PR could be used for more than that in the scope of #2032

Are there changes in behavior for the user?

Not really.

Related issue number

#2032

Checklist

  • [*] I think the code is well written
  • Unit tests for the changes exist
  • Documentation reflects the changes
  • [*] If you provide code modification, please add yourself to CONTRIBUTORS.txt
    • The format is <Name> <Surname>.
    • Please keep alphabetical order, the file is sorted by names.
  • Add a new news fragment into the changes folder
    • name it <issue_id>.<type> for example (588.bug)
    • if you don't have an issue_id change it to the pr id after creating the pr
    • ensure type is one of the following:
      • .feature: Signifying a new feature.
      • .bugfix: Signifying a bug fix.
      • .doc: Signifying a documentation improvement.
      • .removal: Signifying a deprecation or removal of public API.
      • .misc: A ticket has been closed, but it is not of interest to users.
    • Make sure to use full sentences with correct case and punctuation, for example: "Fix issue with non-ascii contents in doctest text files."

@codecov-io
Copy link

Codecov Report

Merging #2034 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #2034   +/-   ##
=======================================
  Coverage   97.05%   97.05%           
=======================================
  Files          38       38           
  Lines        7700     7700           
  Branches     1347     1347           
=======================================
  Hits         7473     7473           
  Misses        103      103           
  Partials      124      124
Impacted Files Coverage Δ
aiohttp/test_utils.py 99.28% <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 6ba5d61...1d4c520. Read the comment docs.

@asvetlov
Copy link
Member

Good catch!
I personally use pytest, we need more feedback from classic unittest adopters.

@asvetlov asvetlov merged commit afbff7b into aio-libs:master Jun 28, 2017
@cecton cecton deleted the improves-test-utils branch June 28, 2017 12:54
cecton added a commit to cecton/aiohttp that referenced this pull request Jul 7, 2017
asvetlov pushed a commit that referenced this pull request Jul 10, 2017
* Improve tox ini (#2031)

* Improve tox.ini to be able to run only some tests

This change will make tox use posargs if there are any or fallback to
"tests" args (which will run the all the tests).

You can now use this command to start a specific test:

tox -e py35 -- -x tests/test_client_connection.py

* Add Python 3.6 to the testing environment

* Fix bad variable used (#2034)
@lock
Copy link

lock bot commented Oct 28, 2019

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.

@lock lock bot added the outdated label Oct 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants