thread/queue bug

[Peter Hansen]

phil wrote:
> I've never before on any group seen anyone told they
> had a mental block, because they were fishing for info.

I'm sorry if I offended you by using that term.  That
wasn't my intention.  Communications can be difficult
in an online forum.  For example, I would normally find
the phrase "fishing for info" to be offensive, but in
this case I'll assume we got off on the wrong foot and
that there are some different thought patterns involved,
and I'm sure you didn't intend to offend any more than
I did.

My intention with "mental block" was to emphasize as
strongly as I could my conviction that your problem
has *nothing* to do with the fact that you have a .pyc
file instead of a .py, and to encourage you to search
elsewhere, to find another way of getting more information
about the problem.

The one key difference that I can see on the face of
it is that a .pyc, being already compiled, doesn't
need a compilation phase the way a .py file would if
it didn't already have an up-to-date .pyc file
present.

I really doubt this small difference in time is the
source of the trouble, but it's possible.  On the
other hand, when you run with the .py file, if you
run a second time and it still fails, then this is
even less likely to be the problem because it will
compile the .py file only the first time, and the
second time it will use the .pyc file just like
when you don't even have the .py file around.

And I could help more, being fairly experienced with
threading issues and race conditions and such, but
as I tried to indicate in the first place, you've
provided next to no useful (IMHO) information to
let anyone help you more than this... sorry.  (And,
again, no offense intended by that statement.)

-Peter