Comment 16 for bug 515236

It is great to see responsiveness like this. Please pardon me if I seem slow in the uptake on some things, technically or collaboratively. I fear some of my comments may veer off-topic; I'll look for a better home for these.

@#15
Hi Robo, I like the random shuffle idea too; just take a look at page two of my attachment in post #2 for my take on it. Highlights would be: the empty space must hit all locations at least once; purely random movement of the empty space won't insure mixing; a couple of methods to randomly apply that will mix it up okay. The inversion method was a cool insight though.

@#14
Thanks Joe. My reason for not editing the files off of "/usr/lib/.." were twofold -- (1) root ownership and (2) doing a poor-man's RCS, a quick and dirty way to exercise the source without worrying about changing my copy of the main line. As far as the working environment, I've been used to looking at registers and variables as I step through code and setting break points. I'd be interested in doing so while learning Python.. if it's possible. Maybe it's built into the native interpreter, I don't know. Is what you suggested I do what you do? I've downloaded some tools for evaluation. I don't have a favorite code editor yet.

How about the rest of you? What are your top tools that you use day in day out to get/put, edit and test your Python code?
 -- vim, gedit, emacs, activeedit, winpdb, codeblocks, netbeans, eclipse.. pros and cons.. whatever you'd like to share.

 I guess I'll have to put further questions like this in a different thread.. not sure where yet...