Peter Hansen <[EMAIL PROTECTED]> writes:
> Kirk Job Sluder wrote:
>> I agree with this approach. For me, there has to be a certain level of
>> complexity before I reach for python as a tool.
>
> For me as well. In my case, the key question is "is this bash script
> going to be longer than two lines?". If it would be, the Python
> approach will be done faster and will be more maintainable, since I
> often don't look at those scripts again for months and would tend to
> forget any bash syntax that I've learned in the meantime.
I tend to switch from sh to python when I start writing a loop. A long
list of repeated commands - even with conditionals - isn't to bad. But
when you start forking processes in a loop, it's time to use a more
powerful tool.
<mike
--
Mike Meyer <[EMAIL PROTECTED]> http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.
--
http://mail.python.org/mailman/listinfo/python-list
