Thanks! That is exactly what I needed. I can now trace through the enclosing SQLA calls now.
On Friday, January 9, 2015 at 5:40:58 PM UTC-8, Lycovian wrote: > > I'm attempting to debug a custom dialect using pudb. Once my custom > create_connect_args function returns to strategies.py pudb stops showing me > the source. I assume this is because SQLAlchemy is installed as a bdist. > Is there a way to install SQLAlchemy such that the source is part of the > distribution egg so that I can also trace through the source? BTW, my > dialect relies on pyodbc as well and I see that pyodbc.so is part of the > egg so possibly this is why I can't see the SQLA source? Just a guess. > > > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
