On 10.06.2017 03:43, RjOllos wrote:
I think it's worth considering to just do a switch to Python 3.5+ in
Trac 1.5.1 rather than supporting 2.7 and 3.5+.
* Python 2.7 is end-of-life in 2020 (PEP:0373)
* Optimistically, Trac 1.6 would be July 2018
* We could continue to support Trac 1.4.x through 2020
* Targeting fewer python versions can increase development velocity on
the trunk
* We can take advantage of the improvements in Python3 without concern
for a six compatibility layer
* Backward compatibility for old python versions will likely continue
to be less important with the adoptions of containers and other
isolated environments
I would like to look to the future, improve my proficiency in the
latest versions of Python focus and focus on adding features. It feels
like we've had an excessive focus on the past (e.g. active development
supporting Python 2.5 continues for Trac 1.0-stable) and I think it
hinders the project. I can think of some counterpoints, I just don't
think any of them are as important as the points I've listed. Django
is dropping support for Python2 in the next major release (1).
Are there any arguments for needing to continue to have the latest
stable release run on Python 2.7 in mid-to-late 2018? It would seem to
me that anyone wanting to stay with the latest Trac can spend the next
12-18 months on their migration plan for this tiny web app.
- Ryan
Sounds reasonable to me, personally. My impression has also been that
the project suffers from this "focus on the past". (I would include
"still using SVN" and "contribution model by patches" here.)
[OT: I wonder if it would be possible to create a GitHub bot that posts
all GitHub issues, PR's and comments to Trac tickets, and a Trac plugin
that posts Trac replies back to GitHub.]
One big concern for me is Mercurial support. The current MercurialPlugin
means Trac and Mercurial must run on the same Python version. And
Mercurial has long been very opposed to Python 3 support. This now seems
to have changed somewhat, but I think it's still unclear when it will be
supported.
https://www.mercurial-scm.org/wiki/SupportedPythonVersions#Python_3.x_support
https://www.mercurial-scm.org/wiki/Python3
Possibly switching to the server-command protocol would help there, as
Mercurial could then run on its own separate Python version.
https://trac.edgewall.org/ticket/10411
- Peter
--
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.
