Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Document ctypes support policy (or rather, the lack thereof) #211

Open
@ncoghlan

Description

@ncoghlan

In writinghttps://bugs.python.org/issue30478#msg294528, I went looking in thectypes docs to see if there was a note saying that it's relatively trivial to trigger segfaults with that module, so if you get a crash when using it, our default assumption is going to be that the bug is in how ctypes is being used, rather than being in ctypes itself.

However, I didn't see any such note, and I don't think we have anything explicit in the developer guide advising triagers to use "closed/third party" as the default resolution for such reports, with a pointer to thefaulthandler module as a tool for investigating further (either the stdlib one for 3.x users, or the PyPI one for 2.7).

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp