Refactor python2 handling after increasing test coverage

[willingc]

There's a bit of inconsistency of how Python2 is being used alongside Python 3. After test coverage is at 80% ish, we should consider refactoring which libraries are used to best support python2 and python3 so that the code base essentially handles both with a minimum of "if 2" or "if 3". Focus on selecting the best practices for migration from 2 to 3.

[willingc]

cc / @MSeal @betatim @rgbkrk

[betatim]

I think there is already use of six so we should build on that and switch things which deviate from that to using six.

For example

papermill/papermill/tests/test_execute.py

Lines 18 to 20 in 3fa2fab

	python_2 = sys.version_info[0] == 2
	PYTHON = 'python2' if python_2 else 'python3'
	execute_notebook = partial(execute_notebook, kernel_name=PYTHON)

should use six.PY2.

[MSeal]

Yes agreed to all of that. Between six and future we should be able to get the explicit branching factor down a lot.

[MSeal]

Gonna close this issue, as more likely we'll be removing python 2 support before we do more of this. Also our test coverage is much higher now with the existing code.