From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Sat, 25 May 2019 13:14:45 +0000 (-0400)
Subject: Use py.test for versioned_history tests, nose no longer runs
X-Git-Tag: rel_1_3_4~4
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=047056157cb9d9c4623d472feaa68ee8f44937c7;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

Use py.test for versioned_history tests, nose no longer runs
without warnings under python 3

Fixes: #4697
Change-Id: I46d395d3b6642acd9317e27d6a5723ae5201e877
(cherry picked from commit 0694c7f272819d013b5e1931f1baf0ebfb05e666)
---

diff --git a/examples/versioned_history/__init__.py b/examples/versioned_history/__init__.py
index e6db1fc2ca..1d271fb626 100644
--- a/examples/versioned_history/__init__.py
+++ b/examples/versioned_history/__init__.py
@@ -7,10 +7,13 @@ Compare to the :ref:`examples_versioned_rows` examples which write updates
 as new rows in the same table, without using a separate history table.
 
 Usage is illustrated via a unit test module ``test_versioning.py``, which can
-be run via nose::
+be run via ``py.test``::
+
+    # assume SQLAlchemy is installed where py.test is
+
+    cd examples/versioned_history
+    py.test test_versioning.py
 
-    cd examples/versioning
-    nosetests -v
 
 A fragment of example usage, using declarative::