Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2002-April/023182.html below:

[Python-Dev] trace.py and the obscurity of Tools/scripts/ (was: Unittest list)

• Previous message: [Python-Dev] trace.py and the obscurity of Tools/scripts/ (was: Unittest list)
• Next message: [Python-Dev] trace.py and the obscurity of Tools/scripts/ (was: Unittest list)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

>>>>> "SM" == Skip Montanaro <skip@pobox.com> writes:

  zooko> So in terms of `trace.py', it is a widely useful tool and
  zooko> already has a programmatic interface.  Being added to the
  zooko> hallowed Python Standard Library would be a major step up in
  zooko> publicity and hence usage.  It would require better docs
  zooko> regarding the programmatic usage.

  SM> It's speed cries out for a rewrite of some sort.  I haven't
  SM> thought about it, but I wonder if it could be layered on top of
  SM> hotshot.

Can any of the handler methods be re-coded in C?  The hotshot changes
allow you to install a C function as a trace hook, but doesn't the
trace function in trace.py do a fair amount of work?

Jeremy

• Previous message: [Python-Dev] trace.py and the obscurity of Tools/scripts/ (was: Unittest list)
• Next message: [Python-Dev] trace.py and the obscurity of Tools/scripts/ (was: Unittest list)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4