Comments on: Colourizing Python Print Statements http://blog.quaternio.net/2009/05/18/colourizing-python-print-statements/ Mon, 06 Sep 2010 07:32:22 -0400 http://wordpress.org/?v=2.8.6 hourly 1 By: Stefan http://blog.quaternio.net/2009/05/18/colourizing-python-print-statements/comment-page-1/#comment-1104 Stefan Sun, 30 Aug 2009 22:14:16 +0000 http://blog.quaternio.net/?p=380#comment-1104 I recently found this handy trick that accomplishes something similar by auto overriding the behavior of sys.stdout to indent output to show how deep your print statement is in the call stack. Most of the time it works effortlessly, and even in those cases where it does not, it's pretty simple to hack up the logic of indent_level() to fit your code. Works on windows too! ;) http://code.activestate.com/recipes/411791/ I recently found this handy trick that accomplishes something similar by auto overriding the behavior of sys.stdout to indent output to show how deep your print statement is in the call stack. Most of the time it works effortlessly, and even in those cases where it does not, it’s pretty simple to hack up the logic of indent_level() to fit your code.

Works on windows too! ;)

http://code.activestate.com/recipes/411791/

]]> By: SetJmp http://blog.quaternio.net/2009/05/18/colourizing-python-print-statements/comment-page-1/#comment-1056 SetJmp Thu, 27 Aug 2009 15:12:29 +0000 http://blog.quaternio.net/?p=380#comment-1056 The trick is best described as terminal-specific rather than a bashism. For best practice when using this technique to dump data analytics I think a scheme has to be developed for switching between screen dumping (viewing data in real time on the terminal) and viewing in other tools--those color codes are not so fun when you are trying to view the text in emacs or less. The trick is best described as terminal-specific rather than a bashism. For best practice when using this technique to dump data analytics I think a scheme has to be developed for switching between screen dumping (viewing data in real time on the terminal) and viewing in other tools–those color codes are not so fun when you are trying to view the text in emacs or less.

]]> By: Nick Peters http://blog.quaternio.net/2009/05/18/colourizing-python-print-statements/comment-page-1/#comment-403 Nick Peters Sat, 23 May 2009 18:01:45 +0000 http://blog.quaternio.net/?p=380#comment-403 Very cool Jessy. I just started getting into python, so thanks for sharing! Very cool Jessy. I just started getting into python, so thanks for sharing!

]]> By: Jessy http://blog.quaternio.net/2009/05/18/colourizing-python-print-statements/comment-page-1/#comment-397 Jessy Wed, 20 May 2009 01:43:51 +0000 http://blog.quaternio.net/?p=380#comment-397 you dare to doubt my colour naming scheme?! (actually, it totally wasnt mine, and, i agree :). i wonder if it would be better on another terminal.). you dare to doubt my colour naming scheme?! (actually, it totally wasnt mine, and, i agree :) . i wonder if it would be better on another terminal.).

]]> By: Ben McGraw http://blog.quaternio.net/2009/05/18/colourizing-python-print-statements/comment-page-1/#comment-396 Ben McGraw Tue, 19 May 2009 23:42:34 +0000 http://blog.quaternio.net/?p=380#comment-396 That magenta is not. That magenta is not.

]]>