]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commitdiff
Use py.test for versioned_history tests, nose no longer runs
authorMike Bayer <mike_mp@zzzcomputing.com>
Sat, 25 May 2019 13:14:45 +0000 (09:14 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Sat, 25 May 2019 13:15:46 +0000 (09:15 -0400)
without warnings under python 3

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

examples/versioned_history/__init__.py

index 7478450ac0d2e85f940a837664c9dfb34c48e3ac..cfdf3c684c25814c9eee179e57d894af47dcb7c6 100644 (file)
@@ -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::