Building things with setup.py

[James Stroud]

Ben Finney wrote:
> James Stroud <jstroud at mbi.ucla.edu> writes:
> 
>> <rant>I try things until a build works. I consider everything I do
>> until acquiring a working build as necessary. Going back to see
>> exactly what I did to make things work is not a viable option
> 
> Before trying such "I don't know what I need to do, but I'm going to
> want to know after I do it" procedures, I usually start 'script' in
> the shell session and then start all my experimenting. ('script' is a
> tool from BSD available on most GNU/Linux distributions as well.)
> 
> That way, the entire session, fumbling dead-ends and all, is available
> for later examination and trimming back to a "what I did to get it
> working" document.
> 

Beautiful suggestion. I've never even heard of that before. With OS X 
Terminal.app, I can buffer "unlimited lines" on my 6 year old ibook I 
use at home and on the road. But at work, on my brand new dual pentium, 
I've found myself limited to the thousand or so lines that konsole gives me.

James