From 838e758cf72708c821ecfb7f3fe945e74a3934ae Mon Sep 17 00:00:00 2001 From: holger krekel Date: Sat, 7 Jul 2012 07:40:51 +0200 Subject: [PATCH] exit with errno instead of always signalling success, thanks John Anderson --- CHANGELOG | 1 + doc/en/goodpractises.txt | 4 +++- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/CHANGELOG b/CHANGELOG index e71727514..4f7fff9e9 100644 --- a/CHANGELOG +++ b/CHANGELOG @@ -1,6 +1,7 @@ Changes between 2.2.4 and 2.3.0.dev ----------------------------------- +- fix "python setup.py test" example to cause a proper "errno" return - fix issue165 - fix broken doc links and mention stackoverflow for FAQ - fix issue139 - merge FuncargRequest and Item API such that funcarg-functionality is now directly available on the "item" diff --git a/doc/en/goodpractises.txt b/doc/en/goodpractises.txt index 89836b659..e294eefa8 100644 --- a/doc/en/goodpractises.txt +++ b/doc/en/goodpractises.txt @@ -103,6 +103,7 @@ which means its really easy to extend its test command to support running a pytest from test requirements:: from setuptools.command.test import test as TestCommand + import sys class PyTest(TestCommand): def finalize_options(self): @@ -112,7 +113,8 @@ to support running a pytest from test requirements:: def run_tests(self): #import here, cause outside the eggs aren't loaded import pytest - pytest.main(self.test_args) + errno = pytest.main(self.test_args) + sys.exit(errno) setup( #...,