cyclic reference in ctypes CFunctionType objects

[theller]

BPO	2682
Nosy	@loewis, @theller
Files	cthunk.patch

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields: ```python assignee = 'https://github.com/theller' closed_at = created_at = labels = ['ctypes', 'performance'] title = 'cyclic reference in ctypes CFunctionType objects' updated_at = user = 'https://github.com/theller' ``` bugs.python.org fields: ```python activity = actor = 'theller' assignee = 'theller' closed = True closed_date = closer = 'theller' components = ['ctypes'] creation = creator = 'theller' dependencies = [] files = ['10086'] hgrepos = [] issue_num = 2682 keywords = ['patch'] message_count = 7.0 messages = ['65733', '65738', '65739', '65741', '65775', '65801', '65806'] nosy_count = 2.0 nosy_names = ['loewis', 'theller'] pr_nums = [] priority = 'normal' resolution = 'fixed' stage = None status = 'closed' superseder = None type = 'resource usage' url = 'https://bugs.python.org/issue2682' versions = ['Python 2.6', 'Python 2.5', 'Python 3.0'] ```

[theller]

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.

[61337411-43fc-4a9c-b8d5-4060aede66d0]

Can you please elaborate your (apparent) concerns about this patch? IOW, why did you not check it in?

[theller]

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.

[theller]

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.

[theller]

> 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?

[61337411-43fc-4a9c-b8d5-4060aede66d0]

Martin, are there any problems with this approach?

No, it's fine. I was just puzzled.

[theller]

Also fixed in release25-maint, rev 62504.