Running Futurize:

Now that have manually run most of the files, run futurize on a copy and see what would be changed. Follow Matt's list below.

Checklist of files to run Futurize on:

First-Pass, Exploring Futurize

Have Run Futurize and Checked results:

Note: when simple, the suggested changes are added below the filename. When complexe I describe the changes requested by "futurize."

Note: useful SO discussion regarding why "builtins" is used. See also here: http://python-future.org/imports.html

Pros and cons:

Pros:
- builtins will allow "future" versions of range, particularly, to run in the code. This means consistent behavior (as much as can be made) between Py2 and Py3 code.
Cons:
- Anaconda appears to install builtins automatically, but if user has "cooked their own" Python install, they will need to manually install "builtins."

So I am going to run futurize on all the files, one by one, and manually make the edits, and then manually run

...ok, have seen enough to be convinced to run futurize and then double-re-run the code.

Step 1: tag the commit prior to doing all this.

Done -- see tag "prefuturize."

Step 2: Run futurize on all the core files

... execute suggestions, and then test-run some of the main files.

Using these two commands to futurize, as it will just spit out the text itself:

# First command: look at the suggested changes; if reasonable run second command
futurize filename.py >> ~/workspace/HARK-1/nate-notes/futurize_notes.md
# Second command: same as above but with "-w" (write to file) to actually implement changes 
futurize -w filename.py >> ~/workspace/HARK-1/nate-notes/futurize_notes.md

...note that results are appended to a notes file. This way we can look up what was changed and what might have gone wrong. This ntoes file will be included here as well.

Running Futurize Workspace - npalmer-professional/HARK-1 GitHub Wiki