From ed57b8e08a34c0c80e7e1abc0c28400feb2f7404 Mon Sep 17 00:00:00 2001 From: captainCapitalism <32553875+captainCapitalism@users.noreply.github.com> Date: Thu, 19 Dec 2019 11:35:52 +0100 Subject: [PATCH 1/2] invocation in last section 'pythonpath.rst' title swapped The order of invocations 'python -m pytest' and 'pytest' are different in the header and the explanation. Me being lazy reading about the behaviour of 'former' looked up quickly the title and rushed to implementation to discover it actually works the other way - as stated in the documentation. So I propose to switch the order in the title to achieve consistent ordering and not confusing somebody like me again! :) --- doc/en/pythonpath.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/en/pythonpath.rst b/doc/en/pythonpath.rst index 0054acc59..65f7b51c8 100644 --- a/doc/en/pythonpath.rst +++ b/doc/en/pythonpath.rst @@ -74,7 +74,7 @@ This is also discussed in details in :ref:`test discovery`. .. _`pytest vs python -m pytest`: -Invoking ``pytest`` versus ``python -m pytest`` +Invoking ``python -m pytest`` versus ``pytest`` ----------------------------------------------- Running pytest with ``python -m pytest [...]`` instead of ``pytest [...]`` yields nearly From a9608d54e0c8db747abe02644415d95fbd75e441 Mon Sep 17 00:00:00 2001 From: Bruno Oliveira Date: Thu, 26 Dec 2019 08:19:11 -0300 Subject: [PATCH 2/2] Switch the order of the commands back and update the text As suggested during review --- doc/en/pythonpath.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/en/pythonpath.rst b/doc/en/pythonpath.rst index 65f7b51c8..f2c86fab9 100644 --- a/doc/en/pythonpath.rst +++ b/doc/en/pythonpath.rst @@ -74,9 +74,11 @@ This is also discussed in details in :ref:`test discovery`. .. _`pytest vs python -m pytest`: -Invoking ``python -m pytest`` versus ``pytest`` +Invoking ``pytest`` versus ``python -m pytest`` ----------------------------------------------- -Running pytest with ``python -m pytest [...]`` instead of ``pytest [...]`` yields nearly -equivalent behaviour, except that the former call will add the current directory to ``sys.path``. +Running pytest with ``pytest [...]`` instead of ``python -m pytest [...]`` yields nearly +equivalent behaviour, except that the latter will add the current directory to ``sys.path``, which +is standard ``python`` behavior. + See also :ref:`cmdline`.