[issue38100] Spelling error in unittest.mock code

Change by Stéphane Wirtel : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.7 ___ Python tracker ___

[issue38100] Spelling error in unittest.mock code

miss-islington added the comment: New changeset 7aae4f004e69ebec011098f85ab232e2778a0ca4 by Miss Islington (bot) (Stéphane Wirtel) in branch '3.7': [3.7] bpo-38100: Fix spelling error in unittest.mock code (GH-16195) https://github.com/python/cpython/commit/7aae4f004e69ebec011098f85ab232e2778a

[issue38100] Spelling error in unittest.mock code

Change by Stéphane Wirtel : -- pull_requests: +15801 pull_request: https://github.com/python/cpython/pull/16195 ___ Python tracker ___ __

[issue38100] Spelling error in unittest.mock code

Lisa Roach added the comment: (y) Thanks for looking into it Stéphane! -- ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue38100] Spelling error in unittest.mock code

Stéphane Wirtel added the comment: Lisa, I don't close this issue because I would like to know if we have to back port to 3.7. The spelling error does exist into 3.7 -- versions: +Python 3.8, Python 3.9 ___ Python tracker

[issue38100] Spelling error in unittest.mock code

miss-islington added the comment: New changeset cc8edfbd9c66a40e2d405e49b75227a8d2a4dd55 by Miss Islington (bot) in branch '3.8': bpo-38100: Fix spelling error in unittest.mock code (GH-16168) https://github.com/python/cpython/commit/cc8edfbd9c66a40e2d405e49b75227a8d2a4dd55 -- nosy:

[issue38100] Spelling error in unittest.mock code

Stéphane Wirtel added the comment: New changeset a9187c31185fe7ea47271839898416400cc3d976 by Stéphane Wirtel (marcoramirezmx) in branch 'master': bpo-38100: Fix spelling error in unittest.mock code (GH-16168) https://github.com/python/cpython/commit/a9187c31185fe7ea47271839898416400cc3d976 -

[issue38100] Spelling error in unittest.mock code

Change by miss-islington : -- pull_requests: +15797 pull_request: https://github.com/python/cpython/pull/16191 ___ Python tracker ___ __

[issue38100] Spelling error in unittest.mock code

Lisa Roach added the comment: It helps to comment on the issue before making a PR for it to claim it, as now we have 3 PRs all for the same issue :) We will likely accept the first PR that was created (or in this case the first PR that gets a CLA signed for it) -- __

[issue38100] Spelling error in unittest.mock code

Change by Marco Antonio Ramirez Valdes : -- pull_requests: +15778 pull_request: https://github.com/python/cpython/pull/16168 ___ Python tracker ___

[issue38100] Spelling error in unittest.mock code

Change by Maritza Esparza : -- pull_requests: +15774 pull_request: https://github.com/python/cpython/pull/16165 ___ Python tracker ___ _

[issue38100] Spelling error in unittest.mock code

Change by Roundup Robot : -- keywords: +patch pull_requests: +15773 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16164 ___ Python tracker ___ __

[issue38100] Spelling error in unittest.mock code

New submission from Lisa Roach : Good first issue. There is a spelling error in the unittest.mock library, "return_calulator" should be "return_calculator". This is in the `_set_return_value` method in `Lib/unittest/mock.py`. -- components: Library (Lib) keywords: easy, newcomer frie