Menu
▾
▴
#360 unconditional debugprint noise
there are about 150 debugprints without v= argument,
meaning they dont depend on the configured verbosity at
all.
find -name "*.py" | grep -v _darcs | xargs grep
debugprint\( | grep -v "[ ,(]v[ ]*=" | grep -v "^[^
]*:[ ]*#" | less
some of those are in pyutil, most annoying the DoQ
task_free thing.
partial fix (the LBS parts of it) in bakaDARCS
Logged In: YES
user_id=335935
bakaDARCS commited to HEAD.
What does "LBS part of it" mean?
Logged In: YES
user_id=52562
"LBS" --> Local Block Store
Logged In: YES
user_id=335935
I think we should make v a required arg in debugprint.
Thoughts?
Logged In: YES
user_id=52562
Sounds okay to make "v=" required. But what about
http://sourceforge.net/tracker/index.php?func=detail&aid=670983&group_id=43482&atid=436453
[ 670983 ] use the python 2.3 logging module in place of
debugprint
(or alternately the twisted logging module -- whichever is
easier.)