Skip to content
Snippets Groups Projects
Select Git revision
  • d716a0dfe2d1029111db393afaecdb04cc4093de
  • main default protected
  • 3.10
  • 3.11
  • revert-15688-bpo-38031-_io-FileIO-opener-crash
  • 3.8
  • 3.9
  • 3.7
  • enum-fix_auto
  • branch-v3.11.0
  • backport-c3648f4-3.11
  • gh-93963/remove-importlib-resources-abcs
  • refactor-wait_for
  • shared-testcase
  • v3.12.0a2
  • v3.12.0a1
  • v3.11.0
  • v3.8.15
  • v3.9.15
  • v3.10.8
  • v3.7.15
  • v3.11.0rc2
  • v3.8.14
  • v3.9.14
  • v3.7.14
  • v3.10.7
  • v3.11.0rc1
  • v3.10.6
  • v3.11.0b5
  • v3.11.0b4
  • v3.10.5
  • v3.11.0b3
  • v3.11.0b2
  • v3.9.13
34 results

cpython

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Victor Stinner authored and GitHub committed
    Currently, calling Py_EnterRecursiveCall() and
    Py_LeaveRecursiveCall() may use a function call or a static inline
    function call, depending if the internal pycore_ceval.h header file
    is included or not. Use a different name for the static inline
    function to ensure that the static inline function is always used in
    Python internals for best performance. Similar approach than
    PyThreadState_GET() (function call) and _PyThreadState_GET() (static
    inline function).
    
    * Rename _Py_EnterRecursiveCall() to _Py_EnterRecursiveCallTstate()
    * Rename _Py_LeaveRecursiveCall() to _Py_LeaveRecursiveCallTstate()
    * pycore_ceval.h: Rename Py_EnterRecursiveCall() to
      _Py_EnterRecursiveCall() and Py_LeaveRecursiveCall() and
      _Py_LeaveRecursiveCall()
    d716a0df
    History
    Name Last commit Last update