Code formatting and structuring

[lynnpepin]

With this issue, we should have some changes to code format and structure (and establish a style for the project).

A few changes to expect:

• Imports before code
• Snake-case variable names
• No single-character names
• Multi-line strings in place of comments
• Tests outside code (except for oneliners, asserts).

Outside the scope of this issue, but other related changes to keep in mind:

• Sphinx-RTD format docstrings. (Good for generating documentation without maintaining eparate docs.)
• Robust tokenizer for various CSV-esques. (SpaCy for NLP if we need something extreme.)
• Find alternative to yamale?
• Make UTF-8 standard.
• Document usage under python -i foobar.py
• Use Jupyter Notebooks for interactivity, where applicable.

[Jbutler-helpful]

I like the idea of Jupyter Notebooks for interactivity

[Jbutler-helpful]

@devhawk can you review this, I suspect this sort of stuff should end up in the Readme or in a specific style guide.

[Jbutler-helpful]

@devhawk this issue is resolve correct

Is the best practice documented sufficiently in the readme