Incidentally, the same problem is happening when using SPE as my editor. Ordinarily it is able to open sources of imported modules so the user can view the statement where an exception occurred, but in the case of SQLAlchemy modules, it's going after the egg instead of where the .py files actually reside. Again, I don't mind monkeying around to achieve a workaround, but I'm just wondering if I installed SQLAlchemy incorrectly or something, such that the package doesn't report accurately where its sources are. -?-
On May 13, 6:45 pm, Eric Ongerth <[EMAIL PROTECTED]> wrote: > That makes sense. I could do that, or I could just put copies of all > the needed files in the directory where winpdb's looking. > > I guess my question is, why isn't the relevant stuff already in my > site-packages directory as a result of installing SQLAlchemy? I > followed the usual install procedure and the whole thing has been > working fine so far -- until I started using winpdb for the first time > and it looks in the wrong place. Maybe I need to take this up on the > winpdb side instead. > > On May 13, 3:29 am, Paul Johnston <[EMAIL PROTECTED]> wrote: > > > Hi, > > > Here something you could try. Delete the egg and get a SVN checkout of > > SQLAlchemy. Then copy the lib/sqlalchemy directory into your > > site-packages directory (as "sqlalchemy"; omit the "lib/"). This > > bypasses the egg mechanisms, which /may/ help. > > > Paul > > > Eric Ongerth wrote: > > >I'm using winpdb 1.1.2 to debug my sqlalchemy/wxPython app. whenever > > >the current instruction moves inside of an sqlalchemy module, winpdb > > >reports that it's able to continue executing but unable to show me > > >where I am until control passes back out of sqlalchemy. Apparently > > >this is because winpdb is trying to look inside of sqlalchemy's python > > >eggs to follow along, rather than in actual text files. > > > >An example of the messages I'm seeing in winpdb's code window: > > > >Failed to load source file 'build\bdist.win32\egg\sqlalchemy\orm > > >\session.py' from debuggee. > > >You may continue to debug, but you will not see source lines from this > > >file. > > > >Inspecting the relevant directories on my system, I see that build > > >\bdist.win32 is actually empty. Meanwhile build\lib\sqlalchemy\orm > > >holds the file session.py that winpdb needed. > > > >So, I need to change something in order to make winpdb substitute build > > >\lib\sqlalchemy wherever it was trying to look in build\bdist.win32. > > >I don't see any way of changing this behavior in winpdb itself. Can I > > >do something on the sqlalchemy side to straighten this out? Is there > > >something I can change in a source file? Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
