ctypes pointer not always keeping target alive

Open
#46,376 11 comments 0 reactions 1 assignee View on GitHub

@theller is already working on this.

Since Feb 15, 2008.

Assessment

This issue has not been assessed yet.

Description

extension-modules topic-ctypes type-bug
BPO 2123
Nosy @arigo, @theller, @bitdancer
Files
  • x.py: failing test or bogus test?
  • y.py
  • 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:

    assignee = 'https://github.com/theller'
    closed_at = None
    created_at = <Date 2008-02-15.14:24:58.157>
    labels = ['extension-modules', 'type-bug']
    title = 'ctypes pointer not always keeping target alive'
    updated_at = <Date 2013-07-10.10:14:10.589>
    user = 'https://github.com/arigo'
    

    bugs.python.org fields:

    activity = <Date 2013-07-10.10:14:10.589>
    actor = 'christian.heimes'
    assignee = 'theller'
    closed = False
    closed_date = None
    closer = None
    components = ['Extension Modules']
    creation = <Date 2008-02-15.14:24:58.157>
    creator = 'arigo'
    dependencies = []
    files = ['9436', '9438']
    hgrepos = []
    issue_num = 2123
    keywords = []
    message_count = 5.0
    messages = ['62429', '62436', '62453', '84117', '84218']
    nosy_count = 3.0
    nosy_names = ['arigo', 'theller', 'r.david.murray']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'languishing'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue2123'
    versions = ['Python 2.7', 'Python 3.3', 'Python 3.4']
    

    Linked PRs
    • gh-107131
    • gh-107487
    • gh-107488
    • gh-108412
    • gh-108519
    • gh-108688
    • gh-108864
    • gh-136876
    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.