Description

encukou

opened on Apr 28, 2025

Issue body actions

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

• gh-133079: Remove Py_C_RECURSION_LIMIT & PyThreadState.c_recursion_remaining #133080

Activity

1. encukou

   added

   topic-C-API

   on Apr 28, 2025
2. encukou

   self-assigned this

   on Apr 28, 2025
3. picnixz

   added

   type-featureA feature request or enhancementA feature request or enhancement

   interpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)

   on Apr 28, 2025
4. encukou

   added a commit that references this issue on Apr 28, 2025

   pythongh-133079: Remove Py_C_RECURSION_LIMIT & PyThreadState.c_recurs…

   4e1690b
5. colesbury commented on Apr 28, 2025

   

   colesbury

   on Apr 28, 2025

   Contributor

   More actions

   Looks like this will affect greenlet: https://grep.app/search?q=Py_C_RECURSION_LIMIT. Heads up to @jamadden
6. markshannon commented on Apr 29, 2025

   

   markshannon

   on Apr 29, 2025

   Member

   More actions

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

   added a commit that references this issue on Apr 29, 2025

   gh-133079: Remove Py_C_RECURSION_LIMIT & PyThreadState.c_recursion_re…

   0c26dbd
8. encukou commented on Apr 29, 2025

   

   encukou

   on Apr 29, 2025

   MemberAuthor

   More actions

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

   closed this as completedon Apr 29, 2025

Issue actions