Comment on revision r30992344a91fcc108fe0c47f5c3165cdc64bebdd in pychess

0 views
Skip to first unread message

pyc...@googlecode.com

unread,
Dec 13, 2013, 5:56:35 AM12/13/13
to pychess-c...@googlegroups.com
Comment by gbtami:

Score: Positive

General Comment:
Just a little note. No need to use "\n" at the and of log message strings
after we switched to use standard python logging module.

For more information:
http://code.google.com/p/pychess/source/detail?r=30992344a91fcc108fe0c47f5c3165cdc64bebdd

pyc...@googlecode.com

unread,
Dec 13, 2013, 6:41:42 AM12/13/13
to pychess-c...@googlegroups.com
Comment by matt...@gmail.com:

General Comment:
Oh right, good, I'd forgot that.

For more information:
https://code.google.com/p/pychess/source/detail?r=30992344a91fcc108fe0c47f5c3165cdc64bebdd

pyc...@googlecode.com

unread,
Dec 13, 2013, 6:47:12 AM12/13/13
to pychess-c...@googlegroups.com
Comment by matt...@gmail.com:

General Comment:
I'm glad you took care of that bug. I almost raised its priority a few
weeks ago after we'd had the mailing list emails about the deadlocks. It
should make it a lot easier to debug deadlocks, I think.
Reply all
Reply to author
Forward
0 new messages