From 6be6798cdfedeffc0323375a9d095506f8c757ef Mon Sep 17 00:00:00 2001 From: Jeff Widman Date: Tue, 1 Dec 2015 01:41:47 -0800 Subject: [PATCH] Fix spelling: explicitely --> explicitly --- ISSUES.txt | 2 +- _pytest/runner.py | 2 +- _pytest/vendored_packages/pluggy.py | 2 +- doc/en/example/markers.rst | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/ISSUES.txt b/ISSUES.txt index b744a35f1..cc4b3ecc9 100644 --- a/ISSUES.txt +++ b/ISSUES.txt @@ -115,7 +115,7 @@ tags: feature - introduce pytest.mark.nocollect for not considering a function for test collection at all. maybe also introduce a pytest.mark.test to - explicitely mark a function to become a tested one. Lookup JUnit ways + explicitly mark a function to become a tested one. Lookup JUnit ways of tagging tests. introduce pytest.mark.importorskip diff --git a/_pytest/runner.py b/_pytest/runner.py index 6e4f45d5e..6d0f8b57b 100644 --- a/_pytest/runner.py +++ b/_pytest/runner.py @@ -469,7 +469,7 @@ def skip(msg=""): skip.Exception = Skipped def fail(msg="", pytrace=True): - """ explicitely fail an currently-executing test with the given Message. + """ explicitly fail an currently-executing test with the given Message. :arg pytrace: if false the msg represents the full failure information and no python traceback will be reported. diff --git a/_pytest/vendored_packages/pluggy.py b/_pytest/vendored_packages/pluggy.py index 2090dbb4e..2f848b23d 100644 --- a/_pytest/vendored_packages/pluggy.py +++ b/_pytest/vendored_packages/pluggy.py @@ -573,7 +573,7 @@ class _MultiCall: # XXX note that the __multicall__ argument is supported only # for pytest compatibility reasons. It was never officially - # supported there and is explicitely deprecated since 2.8 + # supported there and is explicitly deprecated since 2.8 # so we can remove it soon, allowing to avoid the below recursion # in execute() and simplify/speed up the execute loop. diff --git a/doc/en/example/markers.rst b/doc/en/example/markers.rst index 164f0abc1..789f41ac8 100644 --- a/doc/en/example/markers.rst +++ b/doc/en/example/markers.rst @@ -219,7 +219,7 @@ For an example on how to add and work with markers from a plugin, see .. note:: - It is recommended to explicitely register markers so that: + It is recommended to explicitly register markers so that: * there is one place in your test suite defining your markers