3

My application is invoked from run.py. I've installed Pygments and I'd like to redirect Python's output so that as tracebacks occur, they're formatted in an easier to read format.

This is the command that I've tried, python run.py 2>&1 | pygmentize -l py

Redirecting both stdout and stderr through pygmentize. The pygmentize documentation says that it will read from stdin if no file is provided, "If no input file is given, use stdin, if -o is not given, use stdout."

However, when I redirect like this, no output--errors or log statements or anything else--is output to my terminal.

When I run my command without piping its output into pygmentize, i.e. python run.py 2>&1 I get this output:

INFO:werkzeug: * Running on http://0.0.0.0:5000/
INFO:werkzeug: * Restarting with reloader

Any suggestions?

skyler
  • 8,010
  • 15
  • 46
  • 69
  • 1
    That's strange. When I try your example, it works fine. (I forced a traceback, and it is pygmentized properly.) Can you show us the output of `python run.py 2>&1` (without the pipe to pygmentize)? – btanaka Apr 30 '13 at 18:29
  • @btanaka when I do that I do get output. I updated my question with that test and its output. – skyler Apr 30 '13 at 18:32

1 Answers1

2

pygmentize reads the whole input stream when reading from stdin and only outputs everything if the input stream is closed, so you only will get any output piped through pygments after your first process has ended.

I'm afraid there's little you can do about that. If you want to format a continuous stream, You could only try to write your own wrapper around pygments wich reads the input stream in chunks and feeds that to pygments.

The reason why you don't see any output at all now is that you're probably using Ctrl+C to stop your process in the shell, but that kills both processes. If you use kill to only terminate the server process, then you should see at least the lines you mentioned above going through pygments.

mata
  • 67,110
  • 10
  • 163
  • 162