Fatal Python error: PyThreadState_Get: no current thread

[Ken Kinder]

Sorry about the slow response. Anyway, that sounds like what's going on and I
would appreciate it if you could give me a little more feedback. The situation
is, I initially had a bucket of trouble getting MySQLdb compiled on BSDi, and
since it compiled fine on Linux, I just tried using the same gcc commands that
distutils used on my Linux box with BSDi, which compiled it fine and led to
the PyThread_Get: no current thread

One thing I had to do is add -lpython1.5 to resolve a bunch of unresolved
symbals at link stage; could this be double-binding the module as you describe
below? If so, how else do I resolve all those symbals??

Thanks for your help, this has really been a pain and I'd be very happy to get
it working right.

Mike Fletcher wrote:

> Whenever I've come upon this error I've had two Python DLLs loaded.  You
> should be able to see which DLLs (SOs) are being imported by each module
> using some standard Unix tool.  I'd often have the problem where a release
> library was getting loaded in the debug interpreter so that the release DLL
> got loaded and called without getting initialised (i.e. no thread state was
> created).
>
> HTH,
> Mike
>
> -----Original Message-----
> From: Ken Kinder [mailto:kkinder at tridog.com]
> Sent: Wednesday, November 01, 2000 6:40 PM
> To: Python List
> Subject: Fatal Python error: PyThreadState_Get: no current thread
>
> I just went through hec to get the MySQL DA installed. When I try to use
> it, I get:
>
>     kkinder at tridog1:~/MySQLdb-0.2.2$ python
>     Python 1.5.2 (#11, Nov 17 1999, 22:58:09)  [GCC egcs-2.91.66
> 19990314 (egcs-1.1.2  on bsdos4
>     Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam
>     >>> import MySQLdb
>     Fatal Python error: PyThreadState_Get: no current thread
>     Abort trap
>
> Any ideas?
>
> --
> http://www.python.org/mailman/listinfo/python-list
>
> --
> http://www.python.org/mailman/listinfo/python-list