Christopher Arndt wrote: > TG 1.0.x will go into maintenance mode soon anyway, from the look of > things, so it should be easy to keep 2.3 support there.
That were my thoughts, too. But in TG 1.1 we should really drop Py 2.3. Not only because of the missing decorator syntax, but because of many other small improvements that people simply assume are there, e.g. generator expressions. I experienced that the Py 2.3 tests are broken very quickly, because developers are on Py 2.4 or Py 2.5 and not aware that they are using new features actually. >> I think we should move to 2.4 in TG 1.1 and to 2.5 in TG 2.0. > > Woawoahwoah, easy with the horses. Why drop 2.4 support? What does 2.5 > have that's so crucial to TG that we absolutely need it? Well, it depends on when TG 2.0 will be released of course. I was anticipating that by the time it will be released, Py 2.5 will be the standard already. Maybe I'm too pessimistic about the time frame? ;-) You're right, Py 2.5 has no one big feature that is absolutely needed, but by dropping Py 2.4 we would not have to care about supporting and testing backward compatibility, providing eggs for the old Python version etc. We would also be free to use some of the innovative features such as the with statement. The conditional expressions are very handy in templates and more readable for newbies. There are other niceties such as defaultdict, startswith and endswith with tuples, any() and all(). Py 2.5 also contains sqlite3 and wsgiref. -- Christoph --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
