On Monday, August 22, 2016 at 1:14:35 PM UTC-7, Tim Graham wrote: > > 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>? >
I agree. Trac has been more than generous in supporting old versions of Python, PostgreSQL, etc ..., to the point that it slows development effort. My aim with the "compatible distros" table was to guide us in developing rules for which versions we'll support, rather than making arbitrary choices. https://trac.edgewall.org/wiki/TracDev/ApiChanges/1.3#CompatibleDistros Based on the platforms listed on the table (the ones in bold), we could start supporting Python 3.4+ rather than 3.3+ in Trac 1.3.1+. - 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 [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.
