[ python-Bugs-816476 ] Fatal Python error: GC object already tracked

[SourceForge.net]

Bugs item #816476, was opened at 2003-10-02 06:42
Message generated for change (Comment added) made by tim_one
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=816476&group_id=5470

Category: Python Interpreter Core
>Group: 3rd Party
>Status: Closed
>Resolution: Wont Fix
Priority: 5
Submitted By: Thorsten Henninger (thenninger)
Assigned to: Nobody/Anonymous (nobody)
Summary: Fatal Python error: GC object already tracked

Initial Comment:
Fatal Python error: GC object already tracked

OS: Windows 2000 Server (Service Pack 4)
Python: 2.3.1 (#47)
pycurl: 7.10.6

I got this Fatal Error while fetching Webpages with pycurl.
I do not have any other addiotional information.

This error is reproducible and did not occur with
Python2.2.

Please contact me, if you need further information


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

>Comment By: Tim Peters (tim_one)
Date: 2004-01-01 00:01

Message:
Logged In: YES 
user_id=31435

Closed as (presumed) 3rd-party, won't fix.  There's been no 
followup for 3 months; no other report of this symptom has 
been filed; and someone on c.l.py today reported what 
appears to be exactly the same problem *again* coming from 
use of pycurl.  So all the evidence points to pycurl, and none 
so far to Python.

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

Comment By: Tim Peters (tim_one)
Date: 2003-10-04 13:18

Message:
Logged In: YES 
user_id=31435

Reopening until we know more.

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

Comment By: Thorsten Henninger (thenninger)
Date: 2003-10-02 14:07

Message:
Logged In: YES 
user_id=878819

thank you, that makes sense!
i will notice pycurl and have a look in th pycurl source!


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

Comment By: Tim Peters (tim_one)
Date: 2003-10-02 12:25

Message:
Logged In: YES 
user_id=31435

You should report this to the pycurl project.  The specific 
error message you report is new in Python 2.3, doing a check 
for errnoneous usage of the Python C API.  That check didn't 
exist in Python 2.2.

While it's possible there's a previously unreported error in 
Python 2.3 here, it's much more likely that the problem is in 
pycurl's C code, and that the error there simply went 
undetected before Python 2.3, appearing to work by luck.

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

Comment By: Michael Hudson (mwh)
Date: 2003-10-02 06:51

Message:
Logged In: YES 
user_id=6656

Why do you think this is a bug in Python and not pycurl?

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=816476&group_id=5470