it was a mistake hidden by a traceback error. i was using a library class method as an object method, and the class method constructs an object in it.
On 1/14/21, Karl <[email protected]> wrote: > (to clarify, a line number between two of them, not the output call, > was in the traceback) > adding output to the function that calls that one > > On 1/14/21, Karl <[email protected]> wrote: >> None of my output statements, which I only added to that method, >> output anything, but one of them is listed in the traceback. I >> rebuild just to make sure. >> >> On 1/14/21, Karl <[email protected]> wrote: >>> The line is a call to python's asyncio functions, but none of the >>> function content is in the traceback. >>> >>> I add output statements to determine when the the instruction pointer >>> is jumping. >>> >>> On 1/14/21, Karl <[email protected]> wrote: >>>> The problem still occurs, with a different line in the same method >>>> listed in the traceback. >>>> >>>> It used to line 84. Now it is line 83. But because I added some >>>> module-scope definitions, the method body has shifted down and it's a >>>> different part of the logic. >>>> >>> >> >
