On 11/11/05, Bob Ippolito <[EMAIL PROTECTED]> wrote: > Unless someone stands up and is willing to continuously test > TurboGears against dated versions of Python on the platforms which > still use it and patch when necessary, it seems like a lost cause. > However, I'm not a TG developer, so my assessment doesn't necessarily > carry any weight with the people you're trying to convince.
This is roughly the stance I'm taking. I've started using Python 2.3 style in general for my work inside TurboGears itself, to make it easier should someone step up with a patch to smooth out all of the wrinkles. Ultimately, though, I use 2.4, so thorough testing on 2.3 will depend on someone who more regularly uses that version. Python 2.4.2 is the most stable, fastest Python available. 2.4.x has been the stable release for nearly a year. 2.4 is not bleeding edge software. I think it's a good platform to build from. I do understand that, deployment-wise, you can't get easier than the vendor-installed Python. So, in a nutshell: 2.3 support is possible because 2.3 is supported by CherryPy, SQLObject and Kid. If someone wants to verify 2.3 versions of TurboGears, I'm fine requiring that the TurboGears core uses only 2.3 features. Kevin
