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

Showing content from https://mail.python.org/pipermail/python-dev/2002-April/023097.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 ]

 Barry A. Warsaw <barry@zope.com> wrote:
>
> That's what I think I meant,... yeah!  IOW, convert the script to a
> library module, with a main() and leave a little driver in the
> Tools/scripts directory.

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

Anything else that would be required for trace to make this transition?

Regards,

Zooko

Zooko.Com -- Security and Distributed Systems Engineering

• 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