On 8/8/07, greg <[EMAIL PROTECTED]> wrote:
> Istvan Albert wrote:
> > A solution would be writing the code with a logging function to begin
> > with, alas many times that is out of one's hand.
>
> If the code has been written with calls to a builtin
> print function, the situation isn't much better. You
> could monkeypatch the print function, but that's
> probably worse than swapping sys.stdout.
You can easily modify print in a safe way. Here's an example, that
will work in any recent version of Python:
import sys
def print_(s):
print s
def logger(method):
def wrapper(s):
sys.stderr.write('Logging: %s\n' % s)
method(s)
return wrapper
print_ = logger(print_)
print_('hello')
Running this code will do a regular print of 'hello', as well as
"logging" it to stderr. As a function, you can convert print wholesale
to another logging function, or wrap it transparently like this to
provide additional logging functionality. What do you find wrong with
this sort of "monkeypatching"?
--
Evan Klitzke <[EMAIL PROTECTED]>
--
http://mail.python.org/mailman/listinfo/python-list
