gh-117649: Raise ImportError for unsupported modules in free-threaded build#117651
Conversation
…readed build The free-threaded build does not currently support the combination of single-phase init modules and legacy, non-isolated subinterpreters. Note that with isolated interpreters, single-phase init modules already trigger `ImportError`.
As suggested by Petr in the corresponding issue.
|
@encukou, I've updated the PR with your suggestions from #117649 (comment). |
encukou
left a comment
There was a problem hiding this comment.
I didn't get to finish a full review today, submitting what I have so far.
Co-authored-by: Petr Viktorin <encukou@gmail.com>
Co-authored-by: Petr Viktorin <encukou@gmail.com>
ericsnowcurrently
left a comment
There was a problem hiding this comment.
Aside from possible comments and using "expected failure" in tests, LGTM.
|
When you're done making the requested changes, leave the comment: |
|
Thanks for the review @ericsnowcurrently. I've changed the skips to expected failures and added comments pointing to gh-117649. I have made the requested changes; please review again |
|
Thanks for making the requested changes! @encukou, @ericsnowcurrently: please review the changes made to this pull request. |
ericsnowcurrently
left a comment
There was a problem hiding this comment.
LGTM
Thanks for making those changes. They should really help.
|
|
I'm looking into the file descriptor leak (in |
…readed build (python#117651) The free-threaded build does not currently support the combination of single-phase init modules and non-isolated subinterpreters. Ensure that `check_multi_interp_extensions` is always `True` for subinterpreters in the free-threaded build so that importing these modules raises an `ImportError`.
The free-threaded build does not currently support the combination of single-phase init modules and legacy, non-isolated subinterpreters. Note that with isolated interpreters, single-phase init modules already trigger
ImportError.--disable-gilbuild #117649