On Tuesday, January 17, 2017 at 11:05:02 AM UTC-8, RjOllos wrote: > > > > On Tuesday, January 17, 2017 at 8:08:59 AM UTC-8, cboos wrote: >> >> Hello, >> >> On 12/30/2016 1:07 AM, i...@iprcom.com wrote: >> > I may be jumping the gun a bit as a 1.3.2 (jinga2) tag hasn't been >> > declared yet, but what is the state of the python3 support progress? >> >> On this topic... >> >> I've just seen the following from Python-announce, it's probably not the >> first time they say it, but it's the first time I pay attention: >> >> > Python 3.4 is now in "security fixes only" mode. This is the final >> stage of support for Python 3.4. Python 3.4 now only receives security >> fixes, not bug fixes, and Python 3.4 releases are source code only--no >> more official binary installers will be produced. >> >> It's great that we can now focus on using only Python 2.7 for trunk, and >> though I'd love to be able to continue to have only that version in >> mind, I see that the interest for supporting Python 3.x is there, so I >> won't stand in the way, and maybe even help out a bit... >> >> But I don't want to have to take into account more quirks than necessary >> by supporting already deprecated 3.x versions. So can we please forget >> about 3.4 support, at the very least? >> >> Supporting 3.5 and 3.6 will "only" triple the maintenance cost for >> running tests and the risks of hitting bugs and quirks specific to this >> or that Python version (we already were there). Personally I'll focus on >> 3.5, I think. >> >> So here's my strong vote for supporting only Python 3.5 and 3.6 for Trac >> 1.3.2, let's forget about the earlier 3.x versions. >> >> -- Christian >> >> P.S: and Ian, it's Jinja2, not jinga2 (nor ginsha ;-) ) >> > > I fully agree with only supporting Python 3.5 and 3.6, along with Python > 2.7. > > My motivation for moving to Python 3.x is similar to your motivation for > not supporting Python 3.4 and earlier. Python 2.7 is in maintenance mode > and won't be supported beyond 2020. Eventually we'll need a plan for moving > off Python 2.7, and having a pathway to 3.x sooner rather than later will > be better for the project. > > I've been working on rebasing Jun's python3 branch (#12130) for the past > week. The tests are passing on Python 2 and I have 6 more errors to fix on > Python 3.6. I'll make the branch public soon since I expect there is a lot > more work to do, including code review. > > - Ryan >
More generally, we've been putting together a table to help guide decisions in which versions of packages to support. My feeling is that we should aim to support the dependencies in the latest LTS version of at least Ubuntu, Debian, and CentOS at the time of a major Trac release. Debian 8 currently has Python 3.4.2, but it looks like Debian 9 will be available long before Trac 1.4, and I'm guessing Debian 9 will have at least Python 3.5. https://trac.edgewall.org/wiki/TracDev/ApiChanges/1.3#CompatibleDistros - Ryan -- 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.
