> > I totally agree. Python is really bad for this anyway on Windows - > because each version tends to break extension binary compatibility, a > new version of Python comes out but it is months before we can really > use it, because the extensions have not been recompiled for that > platform yet. I would rather not see this sort of problem extend to > TurboGears, where a new CherryPy or whatever comes out, fixing problems > I need fixed, but I can't use it because TurboGears won't accept the > new version yet. >
Then TG needs tests to ensure it does work fine against versions it claims to support. If I fix a problem in CherryPy but change its API somewhere else, then you might end up with accepting a version that actually fails at some other point. I'm just trying to say that what seems to be a wise idea might open up another door of a room full of bugs. I think having a set of tests would be the best plan. - Sylvain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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 -~----------~----~----~----~------~----~------~--~---
