Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
Sender: skip.montanaro@gmail.com
In-Reply-To: <694830e3-080c-4e66-90e2-6cbab53be071@googlegroups.com>
References: <694830e3-080c-4e66-90e2-6cbab53be071@googlegroups.com>
Date: Mon, 1 Jul 2013 04:32:32 -0500
Subject: Re: settrace doesn't trace builtin functions
From: Skip Montanaro <skip@pobox.com>
To: skunkwerk <skunkwerk@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: python-list@python.org
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.4058.1372671160.3114.python-list@python.org>
Lines: 65
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:49537

>   I've been using the settrace function to write a tracer for my program,=
 which is working great except that it doesn't seem to work for built-in fu=
nctions, like open('filename.txt').  This doesn't seem to be documented, so=
 I'm not sure if I'm doing something wrong or that's the expected behavior.

I believe that's expected behavior.  Stuff written in Python is
traced.  C functions are not.  It's been a whole lot of years since I
looked at that code though, so I might be misremembering.

> The other option I considered was monkey-patching the open function throu=
gh a wrapper ... but that seemed very brittle to me.

For debugging purposes, practicality beats purity.  I trust you won't
be tracing in a production environment, so fragility shouldn't be a
major concern.  Monkey patching seems entirely appropriate to me.

Python 2.x:

>>> open
<built-in function open>
>>> import __builtin__
>>> open is __builtin__.open
True
>>> _open =3D __builtin__.open
>>> def open(name, mode=3DNone, buffering=3DNone):
...   return _open(name, mode, buffering)
...
>>> __builtin__.open =3D open
>>> open is __builtin__.open
True
>>> open
<function open at 0x82afa3c>

Python 3.x:

>>> import builtins
>>> open
<built-in function open>
>>> open is builtins.open
True
>>> _open =3D builtins.open
>>> def open(file, mode=3D'r', buffering=3D-1, encoding=3DNone,
...          errors=3DNone, newline=3DNone, closefd=3DTrue, opener=3DNone):
...   return _open(file, mode, buffering, encoding, errors, newline,
closefd, opener)
...
>>> _open
<built-in function open>
>>> builtins.open =3D open
>>> open
<function open at 0x1010c18c8>

You can, of course, do this for more builtins.  Presuming you can get
a handle on a function's namespace and modify it, you should be able
to perform the same trick for most functions or methods written in C.

>>> sys._settrace =3D sys.settrace
>>> def settrace(*args, **kwds):
...   return sys._settrace(*args, **kwds)
...
>>> sys.settrace =3D sys._settrace

Totally untested.  No warranties expressed or implied. YMMV...  etc, etc

Skip