From 5eefd80f18ea45cf39202c8c622ebe4fd8aec52b Mon Sep 17 00:00:00 2001 From: Philipp A Date: Fri, 19 Aug 2022 14:52:35 +0200 Subject: [PATCH] no setup.cfg --- doc/en/explanation/goodpractices.rst | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/doc/en/explanation/goodpractices.rst b/doc/en/explanation/goodpractices.rst index c027b61d0..31eaec0c5 100644 --- a/doc/en/explanation/goodpractices.rst +++ b/doc/en/explanation/goodpractices.rst @@ -74,7 +74,6 @@ to keep tests separate from actual application code (often a good idea): .. code-block:: text pyproject.toml - setup.cfg mypkg/ __init__.py app.py @@ -245,7 +244,7 @@ setuptools intends to The test files in the first example would be imported as ``test_app`` and ``test_view`` top-level modules by adding ``tests/`` to ``sys.path``. - This results in the following drawback compared to the import mode ``import-lib``: + This results in a drawback compared to the import mode ``import-lib``: your test files must have **unique names**. If you need to have test modules with the same name, @@ -255,7 +254,6 @@ setuptools intends to .. code-block:: text pyproject.toml - setup.cfg mypkg/ ... tests/