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 <gmk...@gmail.com> 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. >
