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

Barry A. Warsaw barry@zope.com
Thu, 11 Apr 2002 14:07:29 -0400

"TP" == Tim Peters <tim.one@comcast.net> writes:

TP> I don't see how that would be an improvement over leaving them
TP> in the scripts directory (which, btw, doesn't bother me a
TP> bit).

TP> Migration to the library is likely counterproductive unless
TP> the code is rewritten to *be* a library.  Like ndiff was
TP> extensively refactored by two people (me and David Goodger),
TP> over two release cycles, to restructure it as a collection of
TP> reusable classes and functions.  Even so, a much smaller
TP> ndiff.py *still* lives in the scripts directory, because the
TP> specific application of these algorithms-- and cmdline
TP> interface --it supplies don't make sense in a general library
TP> module.

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. I was just thinking that a scripts package might be a convenient place to dump these little thingies. But maybe not.

-Barry