- replace most explicitly-named test objects called "Mock..." with

actual mock objects from the mock library.  I'd like to use mock
for new tests so we might as well use it in obvious places.
- use unittest.mock in py3.3
- changelog
- add a note to README.unittests
- add tests_require in setup.py
- have tests import from sqlalchemy.testing.mock
- apply usage of mock to one of the event tests.  we can be using
this approach all over the place.

1 files changed, 7 insertions, 1 deletions

diff --git a/README.unittests.rst b/README.unittests.rst
index ae7189854..7d052cfd7 100644
--- a/README.unittests.rst
+++ b/README.unittests.rst
@@ -7,12 +7,18 @@ module.  If running on Python 2.4, pysqlite must be installed.
 
 Unit tests are run using nose.  Nose is available at::
 
-    http://pypi.python.org/pypi/nose/
+    https://pypi.python.org/pypi/nose/
 
 SQLAlchemy implements a nose plugin that must be present when tests are run.
 This plugin is invoked when the test runner script provided with
 SQLAlchemy is used.
 
+The test suite as of version 0.8.2 also requires the mock library.  While
+mock is part of the Python standard library as of 3.3, previous versions
+will need to have it installed, and is available at::
+
+    https://pypi.python.org/pypi/mock
+
 **NOTE:** - the nose plugin is no longer installed by setuptools as of
 version 0.7 !  Use "python setup.py test" or "./sqla_nose.py".