Python 2 is EOL soon (2020)

[aphor]

In 2020 upstream Python 2 updates (including security updates) will stop.

"The End Of Life date (EOL, sunset date) for Python 2.7 has been moved five years into the future, to 2020. This decision was made to clarify the status of Python 2.7 and relieve worries for those users who cannot yet migrate to Python 3. See also PEP 466."

https://www.python.org/dev/peps/pep-0373/
https://pythonclock.org/

This will require planning (timeline/goals), architecture (dual python versions or cutover migration), testing, and documentation.

[AdSchellevis]

We know. We're probably going to use a dual python version strategy as of 19.1, leaving the rest of the year to convert the different scripts. some are already compatible, some aren't yet.

[aphor]

Wow. That's not a very friendly response. I was hoping to get some discussion going and maybe provide a couple of PRs.

Ticket closed == topic closed

If this is an open source collaboration project, please show me the open door. How can I help?

[fichtner]

Please don't be surprised if you don't lead with a question or personal stake that makes your post not look like an automated notice.

[aphor]

Thanks for the guidance. Would you welcome PRs to help move the Python code migration along?

[AdSchellevis]

@aphor we certainly do, if compatible with both versions we might consider patches to be include in 19.1, otherwise we rather see them enter a bit later so they can be used with our dev version when both versions are shipped.

Thanks in advance!

[fichtner]

Python 3.6 packages will be in 18.7.7, except for ipaddr as it seems to be in the base installation under 3.3+.

66709dbbfa0
opnsense/tools@c0a105a93eb
opnsense/tools@62fa88cd5d1
opnsense/tools@4f5a745c52f
opnsense/tools@28d826cf0ed
opnsense/tools@d322b6001bc
opnsense/tools@a75e573ad2f8
opnsense/tools@627d147d67c
opnsense/tools@a836b4683e8

[AdSchellevis]

@fichtner nice! thanks!

[fichtner]

and today ticket open == no progress ;)

[aphor]

I have to burn some vacation time this month. I spent some of my copious spare time in the last few weeks setting up a local test environment.

BTW: ipaddr in base python is a little problematic as it doesn't accept RFC compliant scoped local addresses. There is a bolt-on implementation which does though, in saltstack/salt.

[fichtner]

Keep ticket or split into workable chunks of actual tasks?