I don't think releasing a new version of Trac and having it support a Python version whose support ends a few months later brings much value.
Django adopted this policy, "Typically, we will support a Python version up to and including the first Django LTS release whose security support ends after security support for that version of Python ends. For example, Python 3.3 security support ends September 2017 and Django 1.8 LTS security support ends April 2018. Therefore Django 1.8 is the last version to support Python 3.3." The idea is that if you insistent on using an old version of Python, are you likely to want the latest and greatest Trac / Django / <third-party library>? On Wednesday, March 16, 2016 at 5:51:25 AM UTC-4, RjOllos wrote: > > > > On Tue, Mar 15, 2016 at 5:30 PM, Tim Graham <[email protected] > <javascript:>> wrote: > >> 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. >> > > Thanks. I haven't worked with Python3 much, but I guess it's worth > considering supporting Python 3.4+. > > If we do support Python 3.3 in Trac 1.4 though, and stick to a major > release every 12-18 months, we would extrapolate nicely on the pattern > Christian previously noted (1). > > Trac 0.11 - last version to work with Python 2.3 > Trac 0.12 - last version to work with Python 2.4 > Trac 1.0 - last version to work with Python 2.5 > Trac 1.2 - last version to work with Python 2.6 > Trac 1.4 - last version to work with Python 3.3 (released Jun 2017?) > Trac 1.6 - last version to work with Python 3.4 (released Jan 2019?) > > The release dates line up fairly nicely with the end-of-life for the > Python releases (2), preceding them by just a few months. > > - Ryan > > (1) https://groups.google.com/d/msg/trac-dev/nkMUY_8ILF0/xdGVywGqTkYJ > (2) https://docs.python.org/devguide/index.html#branchstatus > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
