You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As @stggh pointed out in #219 (comment), support for Python2 is ending in 2020. As much as I hate to see it go, it seems that it's death is certain, and many projects have pledged to stop supporting it within the next year: http://python3statement.org/
I'm not sure exactly when this change will come to PyAbel (v0.9, circa 2019?), but when it does, it should provide an opportunity to simplify our code, since I recall at least a few occasions where we went a bit out of our way to provide Python2 support.
Here is the list of changes that we should make when we drop Py2 support:
As @stggh pointed out in #219 (comment), support for Python2 is ending in 2020. As much as I hate to see it go, it seems that it's death is certain, and many projects have pledged to stop supporting it within the next year: http://python3statement.org/
I'm not sure exactly when this change will come to PyAbel (v0.9, circa 2019?), but when it does, it should provide an opportunity to simplify our code, since I recall at least a few occasions where we went a bit out of our way to provide Python2 support.
Here is the list of changes that we should make when we drop Py2 support:
We can load
.txt.bz2
files directly usingnp.loadtxt
in the examples, basically undoing what was done in Incrementing version to 0.8.0 and including py2 bz2 support #219.We can do away with
import six
We can get rid of the
from __future__
imports that are on top of most of the .py files:In
example_simple_GUI.py
andexample_GUI.py
, we can simplify the lines like:to
I'll amend this list as we come across more examples of simplifications that we can make when we go Py3-only.
The text was updated successfully, but these errors were encountered: