Guy Streeter
2014-07-29 22:07:10 UTC
As far as I have been able to tell, Python 2 will continue to be distributed
in Fedora, at least for the foreseeable future. Upstream python developers say
they will continue to do security fixes and some bugfixes for python 2.7
through 2020, and possibly longer. Given this, I don't know how important
moving tuna to Python 3 really is.
It looks like it would be a significant undertaking if we do it. In addition
to the syntax changes, which are straightforward, there is the matter of the
Gtk implementation change, and then all of the module dependencies.
python-ethtool and python-schedutils are written in C, and I have no idea if
it's just a matter of recompiling to make them Python 3, or if they need to be
rewritten. python-linux-procfs is written in Python, so it should not be
difficult to port.
Personally, I really want to forget Python 2 and just write in Python 3 from
now on. I'd like to propose some enhancements to the tuna GUI (more on that in
another email), but I don't want to write them in Python 2, especially if they
need to be changed for Python 3 in the future.
Does anyone else have opinions (or knowledge) about Python 3 and future tuna
development? Would anyone like to collaborate on an attempt to port it?
thanks,
--Guy
in Fedora, at least for the foreseeable future. Upstream python developers say
they will continue to do security fixes and some bugfixes for python 2.7
through 2020, and possibly longer. Given this, I don't know how important
moving tuna to Python 3 really is.
It looks like it would be a significant undertaking if we do it. In addition
to the syntax changes, which are straightforward, there is the matter of the
Gtk implementation change, and then all of the module dependencies.
python-ethtool and python-schedutils are written in C, and I have no idea if
it's just a matter of recompiling to make them Python 3, or if they need to be
rewritten. python-linux-procfs is written in Python, so it should not be
difficult to port.
Personally, I really want to forget Python 2 and just write in Python 3 from
now on. I'd like to propose some enhancements to the tuna GUI (more on that in
another email), but I don't want to write them in Python 2, especially if they
need to be changed for Python 3 in the future.
Does anyone else have opinions (or knowledge) about Python 3 and future tuna
development? Would anyone like to collaborate on an attempt to port it?
thanks,
--Guy