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 ;-) ) -- 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.
