> I would argue that the picture should look like this: > > * TurboGears 1.0.x will work on Python 2.3 or greater. > * TurboGears 1.1.x will work on Python 2.4 or greater. > * TurboGears 2.0.x will work on Python 2.4 or greater. > > I just don't see Python 2.5 being as widely deployed yet as 2.4. Give > it a year or two, and then we can start requiring Python 2.5 for > TurboGears 2.1 or 3.0 :)
Screw that, I think TurboGears 2 should be python 3000 only. ;) Ok, just kidding. But if generic functions with pedicate dispatch had made it into python 3.0, it's actually possible that I would have tried to make that argument. But as it is, I think 2.4, 2.5, 2.6, and 3.0 is going to be more than enough versions to try to support. And 2.6/3.0 aren't really that far off! --Mark Ramm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
