|
 |
"jr" <cre### [at] gmail com> wrote:
> it would be useful to hear from people who know the
> code, in which circumstances/situations that error can happen.
Is there a way to grep the source code to find out where that gets spit out, as
a starting point for backtracking?
(I'd recommend 3.6 source, as IIRC 3.7 has all the complicated, hard-to-follow
multithreading. If it's in 3.6, and it's still a mystery, then what is learned
from studying the code can be used as a roadmap to 3.7)
Post a reply to this message
|
|
