| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| Multi-phase init extension modules may now indicate that they support | ||
| running in subinterpreters that have their own GIL. This is done by using | ||
| ``Py_MOD_PER_INTERPRETER_GIL_SUPPORTED`` as the value for the | ||
| ``Py_mod_multiple_interpreters`` module def slot. Otherwise the module, by | ||
| default, cannot be imported in such subinterpreters. (This does not affect | ||
| the main interpreter or subinterpreters that do not have their own GIL.) In | ||
| addition to the isolation that multi-phase init already normally requires, | ||
| support for per-interpreter GIL involves one additional constraint: | ||
| thread-safety. If the module has external (linked) dependencies and those | ||
| libraries have any state that isn't thread-safe then the module must do the | ||
| additional work to add thread-safety. This should be an uncommon case. |
| Back | FazBrowse Home | New Git URL |
Uh oh!
There was an error while loading. Please reload this page.