Any plan to update the codebase to python3 ?

[dmargery]

Hi all,

according to https://pythonclock.org/, in 7 months python2.7 will cease to be a supported release and more and more python projects will stop support for python2 at some point (https://python3statement.org/).

Sticking to python 2.7, especially to its TLS support layer, might become unworkable sooner than acceptable

• inability to connect to AMs or services running an up-to-date stack
• inability to exposes AMs to clients running up-to-date implementations of the protocol or of modern ciphers.

This issue to understand if the topic has been discussed, if there is a plan, or a position on the topic of a transition to python3. Might need discussed in geni-developers mailing list at some point.

[ahelsing]

Seems like it would be worth exploring how large a task it is to upgrade. I would hope it wouldn't be too bad to update this project. Updating everything else that uses this (GENI Clearinghouse, genilib, etc) is another story. But we could consider the python model and start with 2 versions for the 2 versions of python.

[nbastin]

FWIW, the geni-lib codebase currently supports both Python2 and Python3.

[ahelsing]

In 2016 I heard SFA was working on python3.4 compatibility, which would help, if true.

See also issue #776.

[nbastin]

There is a python3 branch in SFA, although I don't know what the state of that is. I've been tinkering around with replacing SFA in VTS to eliminate dependencies on things like M2Crypto, although that is not getting much love at the moment.