Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
N
neo
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
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Stefane Fermigier
neo
Commits
e791dc3f
Commit
e791dc3f
authored
Jun 04, 2016
by
Vincent Pelletier
Committed by
Julien Muchembled
Jul 24, 2016
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Control verbose locking via en environment variable
parent
b7e0ec7f
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
5 deletions
+3
-5
neo/lib/locking.py
neo/lib/locking.py
+3
-5
No files found.
neo/lib/locking.py
View file @
e791dc3f
...
...
@@ -18,14 +18,12 @@ from Queue import Empty
This file defines a VerboseLock class implementing basic lock API and
logging in appropriate places with extensive details.
It can be globaly toggled by changing VERBOSE_LOCKING value.
It can be toggled globally by setting NEO_VERBOSE_LOCKING environment
variable to a non-empty value before this module is loaded.
There is no overhead at all when disabled (passthrough to threading
classes).
"""
VERBOSE_LOCKING
=
False
class
LockUser
(
object
):
def
__init__
(
self
,
message
,
level
=
0
):
...
...
@@ -157,7 +155,7 @@ class VerboseSemaphore(VerboseLockBase):
return
not
self
.
lock
.
_Semaphore__value
if
VERBOSE_LOCKING
:
if
os
.
getenv
(
'NEO_VERBOSE_LOCKING'
)
:
Lock
=
VerboseLock
RLock
=
VerboseRLock
Semaphore
=
VerboseSemaphore
...
...
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