Fatal Python error: PyThreadState_Get

[Gordon Williams]

Thanks Mike,

It was an old Python module that I thought I had recompiled, but evidently
had not.

"Fatal Python error: PyThreadState_Get: no current thread" seems like a
funny error to indicate that there is a problem like this.  It would have
taken me hours/days to track this one down.

Regards,

Gordon Williams


----- Original Message -----
From: "Mike Fletcher" <mfletch at tpresence.com>
To: "'Gordon Williams'" <g_will at cyberus.ca>
Sent: Wednesday, December 20, 2000 6:35 PM
Subject: RE: Fatal Python error: PyThreadState_Get


> Normally it's caused by one module using Python15.dll while the rest of
the
> system is using python20.dll .  Check your pyds using dumpbin to see which
> one is doing the incorrect thing.
>
> HTH,
> Mike

"Gordon Williams" <g_will at cyberus.ca> wrote in message
news:91rcjo$2dtl$1 at news2.ottawa.cyberus.ca...
> Using
> W95
> Python 2.0
> Pythonwin build 135
>
> I am now in the process of converting some python 1.5.2 code to python
2.0.
> I now get the message below.
>
>
> Fatal Python error: PyThreadState_Get: no current thread
>
> abnormal program termination
>
> I'm sending and receiving information in one thread via a serial port.  In
> the 1.5.2 code I was using the Marshal serial module.  As that only works
> with 1.5.2, I have now converted that to use windows native stuff using
Mark
> Hamond's work.
>
> There was a thread earlier this month about this same problem.  I think
that
> they were also using W95.  It was unclear whether it was resolved or how
it
> was resolved.
>
> Before I start tracking the problem down, is this a known problem?  What
> causes it? Any pointers on where I should look first?
>
> Regards,
>
> Gordon Williams
>
>