If Python 3 support for Trac won't be released until 2017, I think there's no need to support Python 3.3 which is end-of-life in September 2017 (already the most recent release of Django supports Python 3.4+, for example). I think Python 3.5+ would be a fine target, but if people feel that Python 3.4 support is important for some reason, it might not add much work. As long as we must maintain Python 2.7 support, we're fairly limited in the Python 3 features we can use anyway.
On Tuesday, March 15, 2016 at 6:35:54 PM UTC-4, anton wrote: > > Hi Ryan, > > I am developping on windows where I use > - python 2.7 (with tools like django) > - C# (Visual Studio 2008) for some stuff, > - php (piwik) > - apache ( with a ntlm module to allow single sign on in out intranet) > - sometime python packages wich contain native C files > (which are compiled by my Visual Studio, > for example the apache modwsgi module) > > Now all python 3.0 - 3.4 use Visual Studio 2010 which is > no more actual, and since I bought a new version (my company) > I bought Visual Studio 2015 of course. > > Now: > - python 3.5 is based on Visual Studio 2015 > - the actual php 7 windows binaries are built with Visual Studio 2015 > - the actual http://www.apachelounge.com windows apache binaries > are built with Visual Studio 2015 ( there exist binaries built with > other Visual Studio versions but Visual Studio 2008 is *no* more > supported. > > So I would like to make the big jump directly to python 3.5, > because I am more comfortable when all my > modules are based on the same compiler so I am sure > that all (necessary) components are binary compatible. > > > Anton > > > > > RjOllos wrote: > > > > > > > On Monday, March 14, 2016 at 12:28:32 PM UTC-7, anton wrote: > >> > >> Hi, > >> > >> this year I wanted to try to switch > >> to python3. > >> > >> I tried to install packages on python 3.5.1 > >> - Genshi: worked > >> - Babel: worked > >> - Trac: I got a message thats its only pyton2 compatible > >> > >> So my little question: is there a roadmap for python3 support > >> in trac? > >> > >> Thanks for a hint > >> > >> Anton > >> > > > > There are recent discussions about this on the mailing list. > > https://groups.google.com/forum/#!msg/trac-dev/Rxqr-4Y0fTU/iCrNqOFj1DgJ > > https://groups.google.com/forum/#!topic/trac-dev/KqWPQWuZ63k > > > > The summary is, we'll add Python 3 support in 2016 and Trac 1.4 will > > support Python 2.7, Python 3.3+. Trac 1.4 will be released in 2017, most > > likely. Also likely, Genshi will be dropped as the templating engine in > > favor of Jinja2. > > > > What is your reason for wanting to run on Python 3.5? > > > > - 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.
