10 Jun
2003
10 Jun
'03
10:37 a.m.
I've done it to find out how often and when open() is called in a large application.
A warning is fine -- even desirable. I'd want to make sure such debugging hacks didn't make it into a release. :)
In this case too, I wouldn't mind warnings. I would mind it if I had to hack my libc to track python-level open() calls =).
In any case, the bytecode compiler isn't going to be able to generate more efficient bytecode for open() calls... --Guido van Rossum (home page: http://www.python.org/~guido/)