Sebastian Spaeth deab62fbd8 Fix the broken thread debugging ... Using threading._VERBOSE=1 is broken since python 2.6 till at least python 3.2, (http://bugs.python.org/issue4188) so we can't use it for our thread debugging. Remove the usage of threading._VERBOSE, and implement a "light thread debug log" that for now outputs information when a new thread is being registered and when it is being unregistered. I am sure we will be able to add more thread debugging information over the time. Besides '-d thread' this will re-enable the usage of -d 'all' for the most verbose debugging of all categories. Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de> Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>		2011-05-05 21:07:24 +02:00
..
__init__.py	Allow to use nicer UI names	2011-03-06 15:33:29 +01:00
Blinkenlights.py	Don't pass list to ui.adding/deletingflags	2011-03-07 21:11:10 +01:00
Curses.py	Remove MultiLock implementation	2011-01-25 19:19:14 +01:00
debuglock.py	Update FSF address	2006-08-12 05:15:55 +01:00
Machine.py	Don't pass list to ui.adding/deletingflags	2011-03-07 21:11:10 +01:00
Noninteractive.py	cleanup import statements and conform to PEP-8	2011-03-14 21:35:33 +01:00
TTY.py	cleanup import statements and conform to PEP-8	2011-03-14 21:35:33 +01:00
UIBase.py	Fix the broken thread debugging	2011-05-05 21:07:24 +02:00