From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Mon, 11 Jun 2012 16:15:15 +0000 (-0400)
Subject: make sure integer is here.  only the C ext doesn't try to call "key_fallback" for... 
X-Git-Tag: rel_0_8_0b1~395
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=e6749b6973de0d43b9ab8991d9a8895e0762cb65;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

make sure integer is here.  only the C ext doesn't try to call "key_fallback" for integer here,
pure python one does.
---

diff --git a/test/aaa_profiling/test_resultset.py b/test/aaa_profiling/test_resultset.py
index 2fc335504f..bb16ea1240 100644
--- a/test/aaa_profiling/test_resultset.py
+++ b/test/aaa_profiling/test_resultset.py
@@ -109,6 +109,7 @@ class RowProxyTest(fixtures.TestBase):
             enumerate(zip(keys, processors, row)):
             for key in keyobjs:
                 keymap[key] = (processor, key, index)
+            keymap[index] = (processor, key, index)
         return RowProxy(metadata, row, processors, keymap)
 
     def _test_getitem_value_refcounts(self, seq_factory):