floraachy
/
pytest2
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #4626 from nicoddemus/goodpractices-pythonpath 

Mention PYTHONPATH semantics in goodpractices.rst
This commit is contained in:
Anthony Sottile 2019-01-09 20:41:53 -08:00 committed by GitHub
parent a0ab5a7cd8 9f6d9efc1d
commit bace28517e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/en/goodpractices.rst
View File

@ -72,8 +72,18 @@ to keep tests separate from actual application code (often a good idea)::
test_view.py test_view.py
... ...
This way your tests can run easily against an installed version This has the following benefits:
of ``mypkg``.
* Your tests can run against an installed version after executing ``pip install .``.
* Your tests can run against the local copy with an editable install after executing ``pip install --editable .``.
* If you don't have a ``setup.py`` file and are relying on the fact that Python by default puts the current
directory in ``sys.path`` to import your package, you can execute ``python -m pytest`` to execute the tests against the
local copy directly, without using ``pip``.
.. note::
See :ref:`pythonpath` for more information about the difference between calling ``pytest`` and
``python -m pytest``.
Note that using this scheme your test files must have **unique names**, because Note that using this scheme your test files must have **unique names**, because
``pytest`` will import them as *top-level* modules since there are no packages ``pytest`` will import them as *top-level* modules since there are no packages