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
e4710cfc
Commit
e4710cfc
authored
Nov 15, 2012
by
Brett Cannon
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Issue #15894: Document why we don't worry about re-acquiring the
global import lock after forking.
parent
1e1e8aa5
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
2 deletions
+5
-2
Python/import.c
Python/import.c
+5
-2
No files found.
Python/import.c
View file @
e4710cfc
...
...
@@ -202,8 +202,11 @@ _PyImport_ReInitLock(void)
if
(
import_lock_level
>
1
)
{
/* Forked as a side effect of import */
long
me
=
PyThread_get_thread_ident
();
PyThread_acquire_lock
(
import_lock
,
0
);
/* XXX: can the previous line fail? */
/* The following could fail if the lock is already held, but forking as
a side-effect of an import is a) rare, b) nuts, and c) difficult to
do thanks to the lock only being held when doing individual module
locks per import. */
PyThread_acquire_lock
(
import_lock
,
NOWAIT_LOCK
);
import_lock_thread
=
me
;
import_lock_level
--
;
}
else
{
...
...
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