You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Confirmed on the main branch, but this isn't related to InterpreterPoolExecutor. ipe_executor._thread_name_prefix does appear to be set to the correct value, and the Thread object name is the right value when checking it directly with ipe_executor._threads.
The problem is that thread names aren't pushed down to subinterpreters, which very well might be a wontfix depending on the complexity of the change. Here's a reproducer for that:
cc @ericsnowcurrently, it might be better to just note this when subinterpreters get documented better. (Though, if that's the case, thread_name_prefix should just get removed from InterpreterPoolExecutor.)
Activity
ZeroIntensity commentedon Oct 24, 2024
Confirmed on the main branch, but this isn't related to
InterpreterPoolExecutor.ipe_executor._thread_name_prefixdoes appear to be set to the correct value, and theThreadobject name is the right value when checking it directly withipe_executor._threads.The problem is that thread names aren't pushed down to subinterpreters, which very well might be a wontfix depending on the complexity of the change. Here's a reproducer for that:
cc @ericsnowcurrently, it might be better to just note this when subinterpreters get documented better. (Though, if that's the case,
thread_name_prefixshould just get removed fromInterpreterPoolExecutor.)