Skip to content

Remove Py_C_RECURSION_LIMIT & PyThreadState.c_recursion_remaining #133079

Closed

Description

@encukou

Both were added in 3.13, are undocumented, and don't make sense in 3.14 due to changes in the stack overflow detection machinery. (On current main they contain dummy values.)

SC exception for removal without deprecation: python/steering-council#288

Linked PRs

Activity

  1. self-assigned this
    on Apr 28, 2025
  2. added a commit that references this issue on Apr 28, 2025
  3. colesbury commented on Apr 28, 2025

    @colesbury
    Contributor

    Looks like this will affect greenlet: https://grep.app/search?q=Py_C_RECURSION_LIMIT. Heads up to @jamadden

  4. markshannon commented on Apr 29, 2025

    @markshannon
    Member

    We may still need this for webassembly builds, as they have two stacks and we need a way to protect against either overflowing.
    #130397

  5. added a commit that references this issue on Apr 29, 2025
  6. encukou commented on Apr 29, 2025

    @encukou
    MemberAuthor

    Is it needed in public headers? If so, could you document it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions