"Basic cleaning and docstringing." branch was enhanced and merged back to default 919:1dc6cb931e11
http://hg.savannah.gnu.org/hgweb/bokeep/rev/1dc6cb931e11

Inspected the diff carefully to verify that it was just comments/docstrings and unsued imports . A second look from someone else would be welcome.

After that, pain stakingly (all night!) started the branch "safe variable renames lost in docstring branch" to incorporate the variable rename changes that had been reversed but were actually all right and as a result had not been merged back above.

As the branch title suggests, the intent is to limit it to function and variable renames from before are safe, they don't get persisted anywhere.

Would like a second opinion (and actual testing) on this one and then it can be safely merged in on time for the 1.1.2 release.

Also branched off from that the "front end plugin enabled/disabled attribute change" branch to incorporate the variable rename acts that had been done and reversed that were dangerous and would break backwards compatibility.

This obviously needs a well planned out semi-automatic migration if the user approves (and backs up first!) and shouldn't happen until the next backwards incompatible release (1.2.0). Don't think we should rush this, once "safe variable renames lost in docstring branch" is merged to default "front end plugin enabled/disabled attribute change" will be very similar to default and shouldn't be too hard to keep mergable back to default with semi-regular merges into the branch.

DocStrings should be added/improved in BoKeep's general framework (aka everything but plugins).

This will help new and intermediate contributors understand how the code works so they can be more efficient and make less mistakes.