From 714a97e45219dd57ab5e8a13023f30687a03fa37 Mon Sep 17 00:00:00 2001 From: Russel Winder Date: Mon, 21 Sep 2015 12:00:48 +0100 Subject: [PATCH] Remove references to distutils as per Issue 766. --- doc/en/goodpractises.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/en/goodpractises.rst b/doc/en/goodpractises.rst index 675ac6a9f..aa954edb3 100644 --- a/doc/en/goodpractises.rst +++ b/doc/en/goodpractises.rst @@ -38,7 +38,7 @@ Choosing a test layout / import rules want to keep tests separate from actual application code (often a good idea):: - setup.py # your distutils/setuptools Python package metadata + setup.py # your setuptools Python package metadata mypkg/ __init__.py appmodule.py @@ -51,7 +51,7 @@ Choosing a test layout / import rules have direct relation between (unit-)test and application modules and want to distribute your tests along with your application:: - setup.py # your distutils/setuptools Python package metadata + setup.py # your setuptools Python package metadata mypkg/ __init__.py appmodule.py @@ -178,10 +178,10 @@ You can tell people to download the script and then e.g. run it like this:: -Integrating with distutils / ``python setup.py test`` --------------------------------------------------------- +Integrating with setuptools / ``python setup.py test`` +------------------------------------------------------ -You can integrate test runs into your distutils or +You can integrate test runs into your setuptools based project. Use the `genscript method`_ to generate a standalone ``pytest`` script::