Dan Jacob wrote:
It seems the problems are not so much in TurboGears itself but with the underlying components - CherryPy in particular recently (see Ian Bicking's comment at http://blog.ianbicking.org/my-cherrypy-rant.html). The problem we have is that although we can control the quality of TG code, we can't control what goes on elsewhere. For example, us poor benighted Windows users haven't had a functioning Toolbox until recently, all because of Kid (and that's only fixed in the SVN, not stable Kid release). I have wanted to add proper localization support to form validation, but that will have to wait until it's in FormEncode(for example, it does not seem to support unicode message strings, which means even lazy_gettext won't work for customizing messages).
One thing I think people should feel comfortable doing is reminding upstream developers if a patch is hanging. Like, oh, a FormEncode patch :-/
Personally I'm also willing to give TG people access to set up a Turbogears branch in the projects I'm working on, so you can apply the patches you are most interested in right away, and cherrypick stuff from the trunk. I'd want to be careful about how some of the version numbers and maybe package names are handled, to minimize confusion, but I don't think it should be too much of a problem. Especially if we can sync everything up when a TG version is actually released.
-- Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
