On 2/9/2015 7:11 PM, Ryan Ollos wrote:/ > > Dropping support for Python 2.6 is an issue really worth discussing. > Keeping supporting for Python 2.6 indefinitely is something that will > really slow us down and make it even harder to get to Python 3.x > someday. We have already committed to supporting Python 2.6 in Trac > 1.2.x, but I'd like to drop support for Python 2.6 starting with 1.3.1. > I'm really tired of testing on multiple versions of Python and worrying > about using incompatible features. The situation has gotten better now > that we don't develop Trac 0.12.x, which supports Python 2.4, but we > still have to worry about Python 2.5 in Trac 1.0.x, and I'm eager to > move on. By this time next year it would be ideal if development was > focused on 1.3.x and we only had to test against Python 2.7. >
I agree. Besides: 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 That sequence looks good to me ;-) -- Christian -- 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 http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
