From 1644a44628f6a09bb992752bf266994afe0e98df Mon Sep 17 00:00:00 2001
From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Mon, 6 Mar 2006 03:10:46 +0000
Subject: a mapper with inheritance will place itself as "dependent" on the
 inherited mapper; even though this is not usually needed, it allows certain
 exotic combinations of mapper setups to work (i.e. the one in the polymorph
 example)

---
 lib/sqlalchemy/sql.py | 1 -
 1 file changed, 1 deletion(-)

(limited to 'lib/sqlalchemy/sql.py')

diff --git a/lib/sqlalchemy/sql.py b/lib/sqlalchemy/sql.py
index a6ddf8cb9..d4312a151 100644
--- a/lib/sqlalchemy/sql.py
+++ b/lib/sqlalchemy/sql.py
@@ -1211,7 +1211,6 @@ class Select(SelectBaseMixin, FromClause):
             self.visit_select(cs)
             for s in cs.selects:
                 s.parens = False
-            print "BUT", id(cs), cs.parens
         def visit_column(self, c):pass
         def visit_table(self, c):pass
         def visit_select(self, select):
-- 
cgit v1.2.1