[Python-bugs-list] [Bug #128965] Crash on Windows (no current thread) with gadfly

[noreply@sourceforge.net]

Bug #128965, was updated on 2001-Jan-15 18:33
Here is a current snapshot of the bug.

Project: Python
Category: Windows
Status: Closed
Resolution: Wont Fix
Bug Group: 3rd Party
Priority: 3
Submitted by: nobody
Assigned to : tim_one
Summary: Crash on Windows (no current thread) with gadfly

Details: Occurs when attempting to use gadly:

> Python 2.0 (#8, Oct 16 2000, 17:27:58) [MSC 32 bit (Intel)] on win32
> Type "copyright", "credits" or "license" for more information.
> >>> import sys
> >>> gadflydir=r"c:\program files\python20\lib\gadfly"
> >>> sys.path.append(gadflydir)
> >>> from gadfly import gadfly
> >>> connection=gadfly()
> >>> connection.startup("mydatabase", r"c:\data")
> >>> cursor = connection.cursor()
> >>> cursor.execute("create table ph(nm varchar, ph varchar)")
> Fatal Python error: PyThreadState_Get: no current thread
>
> abnormal program termination
>

Follow-Ups:

Date: 2001-Jan-25 03:05
By: tim_one

Comment:
More than a week has gone by without a followup, so, as threatened, I'm
just closing this (WontFix, presumed Invalid).  If more info comes in, I'll
reopen it.

-------------------------------------------------------

Date: 2001-Jan-16 17:48
By: tim_one

Comment:
We don't write, maintain or even distribute gadfly.  So unless the
anonymous submitter resurfaces to explain where they got gadfly, and what
Aaron (gadfly's author) had to say about it, I'm going to close this.

-------------------------------------------------------

Date: 2001-Jan-16 06:18
By: gvanrossum

Comment:
The problem is not that Python for Windows hasn't been built with threads
(as the subject originally suggested).  But I don't know what the problem
*is* -- it could well be a bug in gadfly, or it could be a Python bug
triggered by gadfly.

Assigning this to Tim, our universal Windows scapegoat.
-------------------------------------------------------

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=128965&group_id=5470