Move from python 2 to python 3

[mnlevy1981]

Python 2 is only going to be supported through the end of 2019, and many packages are moving development to python 3 only sooner than that. For example, NumPy says

Until December 31, 2018, all NumPy releases will fully support both Python2 and Python3.

Starting on January 1, 2019, any new feature releases will support only Python3.

The last Python2 supporting release will be designated as a long term support (LTS) release, meaning that we will continue to merge bug fixes and make bug fix releases for a longer period than usual. Specifically, it will be supported by the community until December 31, 2019

So I think it might be wise to start thinking about moving from Python 2.7 to 3.6 or 3.7.

[bertinia]

Here's a preliminary list of what needs to be done for python3:

• clone the latest python3 version of ncar_pylib for both cheyenne and DAV to check
  that the necessary post-processing module dependencies are installed
• make sure the external subtree modules are python3 compatible; includes ASAPPyTools, PyAverager, PyReshaper, PyConform, and ILAMB.
• make sure all wrapper scripts are python3 compatible

[nocollier]

ILAMB is not python3 ready, but this is also on my radar. Given that computing centers have moved to having users provide their own python environments, holding on to python 2.7 isn't that important anymore. Nate

…

On Fri, Dec 7, 2018 at 3:09 PM Alice Bertini ***@***.***> wrote: Here's a preliminary list of what needs to be done for python3: - clone the latest python3 version of ncar_pylib for both cheyenne and DAV to check that the necessary post-processing module dependencies are installed - make sure the external subtree modules are python3 compatible; includes ASAPPyTools, PyAverager, PyReshaper, PyConform, and ILAMB. - make sure all wrapper scripts are python3 compatible — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#185 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABRRB9KtnXg4N-nKeFYRhl-EUlfWDBEdks5u2srygaJpZM4ZItYg> .

[kmpaul]

ASAPTools is already Py3 ready. The other tools need to be upgraded, but that should not be hard with packages like six and modernize. Plus, they are smaller codebases.

[nocollier]

Just FYI, I pushed two new ILAMB versions to PyPI and the master branch of the ILAMB repository: * v2.3.1 - last python2 compatible version * v2.4 - python3 only See https://bitbucket.org/ncollier/ilamb for details. Nate

…

On Fri, Dec 7, 2018 at 4:03 PM Kevin Paul ***@***.***> wrote: ASAPTools is already Py3 ready. The other tools need to be upgraded, but that should not be hard with packages like six and modernize. Plus, they are smaller codebases. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#185 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABRRB6uaXlpuTmjBB6c2Y7ER_ZeDhOwCks5u2tevgaJpZM4ZItYg> .

[mnlevy1981]

This is just an example of what @kmpaul mentioned in his comment in December, but @klindsay28 pointed out that PyConform is not py3-compatible at this time. From the readme:

Additionally, the entire package is designed to work with Python v2.7 and up to (but not including) Python v3.0.