I'm not sure what would cause this. Is the set_trace() in some code that does any sort of metaprogramming?
It might also be related to some sort of permissions issue with the source file. Another thought: if you are using Windows or macOS and the filename has uppercase characters, the case insensitive filesystem could be confusing the linecache. I've seen issues with this myself. I recommend avoiding uppercase characters in Python source filenames. Aaron Meurer On Mon, Jan 20, 2020 at 4:07 PM David Carson <[email protected]> wrote: > > Andreas, > > This is the first Python 3 script of any substance I have debugged using pudb. > > I just wrote a trivial script in Python 3 and it did not display this > behavior. Running without the '-m pudb' on the command line worked > correctly--breakpoint encountered, source code displayed. > > On Mon, Jan 20, 2020 at 5:53 PM Andreas Kloeckner <[email protected]> > wrote: >> >> David Carson <[email protected]> writes: >> > I am trying to debug a Python 3 script. When I add a 'set_trace()' call >> > and then run the script normally, the breakpoint is hit but there is no >> > source code displayed. I am running the script in the directory where the >> > script is located. >> >> Interesting. I've never seen this happen. Does this occur for any Py3 >> script you attempt to debug? >> >> Andreas > > _______________________________________________ > Pudb mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ Pudb mailing list -- [email protected] To unsubscribe send an email to [email protected]
