This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: cyclic reference in ctypes CFunctionType objects
Type: resource usage Stage:
Components: ctypes Versions: Python 3.0, Python 2.6, Python 2.5
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: theller Nosy List: loewis, theller
Priority: normal Keywords: patch

Created on 2008-04-24 18:07 by theller, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
cthunk.patch theller, 2008-04-24 18:07
Messages (7)
msg65733 - (view) Author: Thomas Heller (theller) * (Python committer) Date: 2008-04-24 18:07
Zachary Pincus posted a message about this cyclic reference in ctypes
CFunctionType objects.  The reference has the problem that these objects
are cleaned up later than expected.

The attached patch fixes this problem by removing the cyclic reference.
msg65738 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2008-04-24 18:37
Can you please elaborate your (apparent) concerns about this patch? IOW,
why did you not check it in?
msg65739 - (view) Author: Thomas Heller (theller) * (Python committer) Date: 2008-04-24 18:45
> Can you please elaborate your (apparent) concerns about this patch? IOW,
> why did you not check it in?

I have no concerns about the patch, and I am currently committing it.
I'm uploading so that I can points others to it, and (hopefully) to test
it before some alpha release.

It is part of my workflow: I develop a patch, test it locally, upload it
and eventually commit it sonner or later, sometimes changing things
depending on feedback I get.
msg65741 - (view) Author: Thomas Heller (theller) * (Python committer) Date: 2008-04-24 18:57
Fixed in trunk and py3k, committed as rev 62481 (trunk), rev 62484 (py3k).

I'll leave this open until the decision about backporting to
release25-maint is made.
msg65775 - (view) Author: Thomas Heller (theller) * (Python committer) Date: 2008-04-25 09:39
>> Can you please elaborate your (apparent) concerns about this patch? IOW,
>> why did you not check it in?
> 
> I have no concerns about the patch, and I am currently committing it.
> I'm uploading so that I can points others to it, and (hopefully) to test
> it before some alpha release.
> 
> It is part of my workflow: I develop a patch, test it locally, upload it
> and eventually commit it sonner or later, sometimes changing things
> depending on feedback I get.

Martin, are there any problems with this approach?
msg65801 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2008-04-25 17:48
> Martin, are there any problems with this approach?

No, it's fine. I was just puzzled.
msg65806 - (view) Author: Thomas Heller (theller) * (Python committer) Date: 2008-04-25 19:55
Also fixed in release25-maint, rev 62504.
History
Date User Action Args
2022-04-11 14:56:33adminsetgithub: 46934
2008-04-25 19:56:03thellersetstatus: open -> closed
resolution: accepted -> fixed
messages: + msg65806
2008-04-25 17:48:07loewissetmessages: + msg65801
2008-04-25 09:39:39thellersetmessages: + msg65775
2008-04-24 18:57:55thellersetresolution: accepted
messages: + msg65741
2008-04-24 18:45:05thellersetmessages: + msg65739
2008-04-24 18:37:47loewissetnosy: + loewis
messages: + msg65738
2008-04-24 18:07:10thellercreate