All,

Python 2 is on it's way out and will no longer be receiving security
updates after Jan 1st, 2020. [1] Aurora currently has a few components
which are currently only compatible with Python 2 including thermos.
Running Aurora components that are only compatible with Python 2 may become
an increasing security liability from the set sunsetting date.

I've opened up an issue on our Github to track/discuss this issue:
https://github.com/apache/aurora/issues/68

Justin Venus has been kind enough to offer his support and expertise in
this field to help shepherd this really important task.

Right now we're looking for guidance from the community as to the direction
we want to go in:

Do we want to drop support for Python 2 and asks users to migrate to Python
3 ASAP?

or

Do we want to move towards deprecating support for Python 2 slowly over the
next year with an EOL support of (around) the end of 2020 while maintaining
both Python2 and Python3 support until then?

Ideally, we'd go for the second approach but the truth is we're lacking in
devpower. If we go the second route there is no guarantee that we would get
there in time to avoid putting systems at risk.

I'd love to hear everyone's take on this.

-Renan

[1] https://www.python.org/doc/sunset-python-2/

Reply via email to