KHarvey wrote:My point was that what they currently mean is place holder. So in 6 months from now they will still mean place holder. This code is something that I actually wrote in VBScript around 10 or 11 years ago
If they have been place holders for 10 years, is it still worth holding that place?
KHarvey wrote: But when I tried to design a class for this script I couldn't quite figure out how, or maybe why, I would use a class. Pretty much all I could figure out is that I would just be using the variables in a class rather than the variables that I am using now. I guess the point is to move this whole script into a class of it's own?
One part that might be good to split out into a class is reading raw input and processing it into a form that makes it easier to work with in the rest of the script. You might also want to use classes for storing data rather than complicated list/dict structures. Basically, whenever you have a set functions all operating on the same set of variables, those functions fuctions should probably be methods in a class and those variables its data members. If you find that you want to stick the entire script in a class (and the script is sufficiently large), then you probably needs to think about decoupling its parts a bit more. Generally, a program can be broken down into distict parts, each with a specific responsibility.
KHarvey wrote:I prefer vim over emacs.
Amen to that; constantly holding down CTRL gets old fast . If you're using vim then you already have basic auto-completion (the default mapping, IIRC, is <C-n>/<C-p> in insert mode; try ":help i_CTRL-n"). You can get more advanced completetion with ctags. You will also want to install the python-mode bundle. It pre-configures vim for Python development (things like four column indent, expand tabs to spaces, etc) and has some useful tools like pylint (finds bugs in your code -- can save you hours of debugging).