[I] [Python] SafeCallIntoPython should error out if interpreter is finalizing/is not initialized [arrow]

["pitrou (via GitHub)" <gi...@apache.org>]

pitrou opened a new issue, #46945:
URL: https://github.com/apache/arrow/issues/46945

   ### Describe the bug, including details regarding any error messages, version, and platform.
   
   `SafeCallIntoPython` is used to construct a callback that can call into Python at arbitrary times from C++.
   
   In some cases, however, it is too late to be able to execute Python code, or even take the GIL, because the Python interpreter has been finalized. This can happen if some async tasks are still running after the user stopped the operation. An example can be found [here]https://github.com/apache/arrow/issues/43497#issuecomment-3018933031).
   
   This will not be completely error-proof, that will have to wait for https://discuss.python.org/t/pep-788-reimagining-native-threads-new-updates
   
   ### Component(s)
   
   Python


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@arrow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] [Python] SafeCallIntoPython should error out if interpreter is finalizing/is not initialized [arrow]

["pitrou (via GitHub)" <gi...@apache.org>]

pitrou commented on issue #46945:
URL: https://github.com/apache/arrow/issues/46945#issuecomment-3043899855

   cc @AlenkaF 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org