Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
1e4518b4
Commit
1e4518b4
authored
Jan 15, 2011
by
Antoine Pitrou
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Improve description of issues
parent
43d31739
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
10 additions
and
7 deletions
+10
-7
Doc/c-api/init.rst
Doc/c-api/init.rst
+10
-7
No files found.
Doc/c-api/init.rst
View file @
1e4518b4
...
@@ -861,13 +861,16 @@ in one sub-interpreter into a namespace of another sub-interpreter; this should
...
@@ -861,13 +861,16 @@ in one sub-interpreter into a namespace of another sub-interpreter; this should
be done with great care to avoid sharing user-defined functions, methods,
be done with great care to avoid sharing user-defined functions, methods,
instances or classes between sub-interpreters, since import operations executed
instances or classes between sub-interpreters, since import operations executed
by such objects may affect the wrong (sub-)interpreter's dictionary of loaded
by such objects may affect the wrong (sub-)interpreter's dictionary of loaded
modules. (XXX This is a hard-to-fix bug that will be addressed in a future
modules.
release.)
Also note that combining this functionality with :c:func:`PyGILState_\*` APIs
Also note that the use of this functionality is incompatible with extension
is delicate, become these APIs assume a bijection between Python thread states
modules such as PyObjC and ctypes that use the :c:func:`PyGILState_\*` APIs (and
and OS-level threads, an assumption broken by the presence of sub-interpreters.
this is inherent in the way the :c:func:`PyGILState_\*` functions work). Simple
It is highly recommended that you don't switch sub-interpreters between a pair
things may work, but confusing behavior will always be near.
of matching :c:func:`PyGILState_Ensure` and :c:func:`PyGILState_Release` calls.
Furthermore, extensions (such as :mod:`ctypes`) using these APIs to allow calling
of Python code from non-Python created threads will probably be broken when using
sub-interpreters.
Asynchronous Notifications
Asynchronous Notifications
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment