- use class name by itself in flush warnings to prevent overflow of warnings registry

- test suite swaps out warnings.warn with warnings.warn_explicit, to solve warnings registry issue
- explicitly disallow functions from inside test.bootstrap, test.lib being interpreted as tests

1 files changed, 11 insertions, 0 deletions

diff --git a/lib/sqlalchemy/util/langhelpers.py b/lib/sqlalchemy/util/langhelpers.py
index 5c12cf67b..68d9709f8 100644
--- a/lib/sqlalchemy/util/langhelpers.py
+++ b/lib/sqlalchemy/util/langhelpers.py
@@ -684,6 +684,17 @@ def warn_exception(func, *args, **kwargs):
 
 
 def warn(msg, stacklevel=3):
+    """Issue a warning.
+    
+    If msg is a string, :class:`.exc.SAWarning` is used as 
+    the category.
+    
+    .. note:: This function is swapped out when the test suite
+       runs, with a compatible version that uses 
+       warnings.warn_explicit, so that the warnings registry can
+       be controlled.
+       
+    """
     if isinstance(msg, basestring):
         warnings.warn(msg, exc.SAWarning, stacklevel=stacklevel)
     else: